Methods and apparatus for device registration in a quasi-licensed wireless system

ABSTRACT

Apparatus and methods for registering and authenticating a client device with a wireless-enabled network. In one embodiment, the apparatus and methods provide an alternate wireless connectivity link to register an installed high-power fixed wireless apparatus (FWA) or Customer Premises Equipment (CPE) with a managed wireless network infrastructure, such as one utilizing “quasi-licensed” CBRS (Citizens Broadband Radio Service) wireless spectrum or another shared access approach. In one variant, the alternate wireless link comprises a mobile cellular channel established via an application program executing on a mobile device. In another variant, an Internet of Thing Network (IoT) is used for the alternate link. In one implementation, spectrum grants are communicated back the FWA/CPE via the alternate link to enable subsequent CBRS-band high-power operation.

PRIORITY

This application is a continuation of and claims priority to U.S. patentapplication Ser. No. 16/661,865 filed on Oct. 23, 2019, entitled“METHODS AND APPARATUS FOR DEVICE REGISTRATION IN A QUASI-LICENSEDWIRELESS SYSTEM” and issuing as U.S. Pat. No. 11,026,205 on Jun. 1,2021, which is incorporated herein by reference in its entirety.

COPYRIGHT

A portion of the disclosure of this patent document contains materialthat is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent files or records, but otherwise reserves all copyrightrights whatsoever.

BACKGROUND 1. Technological Field

The present disclosure relates generally to the field of wirelessnetworks and specifically, in one or more exemplary embodiments, tomethods and apparatus for a high-power wireless transceiver (e.g.,Consumer Premises Device (CPE)) registration with a wireless network,such as for example those providing connectivity via quasi-licensedtechnologies such as Citizens Broadband Radio Service (CBRS), LSA(Licensed Shared Access), TVWS, or Dynamic Spectrum Allocation (DSA).

2. Description of Related Technology

A multitude of wireless networking technologies, also known as RadioAccess Technologies (“RATs”), provide the underlying means of connectionfor radio-based communication networks to user devices. Such RATs oftenutilize licensed radio frequency spectrum (i.e., that allocated by theFCC per the Table of Frequency Allocations as codified at Section 2.106of the Commission's Rules. In the United States, regulatoryresponsibility for the radio spectrum is divided between the U.S.Federal Communications Commission (FCC) and the NationalTelecommunications and Information Administration (NTIA). The FCC, whichis an independent regulatory agency, administers spectrum fornon-Federal use (i.e., state, local government, commercial, privateinternal business, and personal use) and the NTIA, which is an operatingunit of the Department of Commerce, administers spectrum for Federal use(e.g., use by the Army, the FAA, and the FBI). Currently only frequencybands between 9 kHz and 275 GHz have been allocated (i.e., designatedfor use by one or more terrestrial or space radio communication servicesor the radio astronomy service under specified conditions). For example,a typical cellular service provider might utilize spectrum for so-called“3G” (third generation) and “4G” (fourth generation) wirelesscommunications as shown in Table 1 below:

TABLE 1 Technology Bands 3G 850 MHz Cellular, Band 5 (GSM/GPRS/EDGE).1900 MHz PCS, Band 2 (GSM/GPRS/EDGE). 850 MHz Cellular, Band 5(UMTS/HSPA+ up to 21 Mbit/s). 1900 MHz PCS, Band 2 (UMTS/HSPA+ up to 21Mbit/s). 4G 700 MHz Lower B/C, Band 12/17 (LTE). 850 MHz Cellular, Band5 (LTE). 1700/2100 MHz AWS, Band 4 (LTE). 1900 MHz PCS, Band 2 (LTE).2300 MHZ WCS, Band 30 (LTE).

Alternatively, unlicensed spectrum may be utilized, such as that withinthe so-called ISM-bands. The ISM bands are defined by the ITU RadioRegulations (Article 5) in footnotes 5.138, 5.150, and 5.280 of theRadio Regulations. In the United States, uses of the ISM bands aregoverned by Part 18 of the Federal Communications Commission (FCC)rules, while Part 15 contains the rules for unlicensed communicationdevices, even those that share ISM frequencies. Table 2 below showstypical ISM frequency allocations:

TABLE 2 Frequency Center range Type frequency Availability Licensedusers 6.765 MHz- A 6.78 MHz Subject to local Fixed service & mobileservice 6.795 MHz acceptance 13.553 MHz- B 13.56 MHz Worldwide Fixed &mobile services except 13.567 MHz aeronautical mobile (R) service 26.957MHz- B 27.12 MHz Worldwide Fixed & mobile service except 27.283 MHzaeronautical mobile service, CB radio 40.66 MHz- B 40.68 MHz WorldwideFixed, mobile services & earth 40.7 MHz exploration-satellite service433.05 MHz- A 433.92 MHz only in Region amateur service & radiolocation434.79 MHz 1, subject to service, additional apply the local acceptanceprovisions of footnote 5.280 902 MHz- B 915 MHz Region 2 only Fixed,mobile except aeronautical 928 MHz (with some mobile & radiolocationservice; exceptions) in Region 2 additional amateur service 2.4 GHz- B2.45 GHz Worldwide Fixed, mobile, radiolocation, 2.5 GHz amateur &amateur-satellite service 5.725 GHz- B 5.8 GHz WorldwideFixed-satellite, radiolocation, 5.875 GHz mobile, amateur & amateur-satellite service 24 GHz- B 24.125 GHz Worldwide Amateur,amateur-satellite, 24.25 GHz radiolocation & earth exploration-satelliteservice (active) 61 GHz- A 61.25 GHz Subject to local Fixed,inter-satellite, mobile & 61.5 GHz acceptance radiolocation service 122GHz- A 122.5 GHz Subject to local Earth exploration-satellite (passive),123 GHz acceptance fixed, inter-satellite, mobile, space research(passive) & amateur service 244 GHz- A 245 GHz Subject to localRadiolocation, radio astronomy, 246 GHz acceptance amateur &amateur-satellite service

ISM bands are also been shared with (non-ISM) license-freecommunications applications such as wireless sensor networks in the 915MHz and 2.450 GHz bands, as well as wireless LANs and cordless phones inthe 915 MHz, 2.450 GHz, and 5.800 GHz bands.

Additionally, the 5 GHz band has been allocated for use by, e.g., WLANequipment, as shown in Table 3:

TABLE 3 Dynamic Freq. Selection Band Name Frequency Band Required (DFS)?UNII-1 5.15 to 5.25 GHz No UNII-2 5.25 to 5.35 GHz Yes UNII-2 Extended 5.47 to 5.725 GHz Yes UNII-3 5.725 to 5.825 GHz No

User client devices (e.g., smartphone, tablet, phablet, laptop,smartwatch, or other wireless-enabled devices, mobile or otherwise)generally support multiple RATs that enable the devices to connect toone another, or to networks (e.g., the Internet, intranets, orextranets), often including RATs associated with both licensed andunlicensed spectrum. In particular, wireless access to other networks byclient devices is made possible by wireless technologies that utilizenetworked hardware, such as a wireless access point (“WAP” or “AP”),small cells, femtocells, or cellular towers, serviced by a backend orbackhaul portion of service provider network (e.g., a cable network). Auser may generally access the network at a “hotspot,” a physicallocation at which the user may obtain access by connecting to modems,routers, APs, etc. that are within wireless range.

CBRS and Other “Shared Access” Systems—

In 2016, the FCC made available Citizens Broadband Radio Service (CBRS)spectrum in the 3550-3700 MHz (3.5 GHz) band, making 150 MHz of spectrumavailable for mobile broadband and other commercial users. The CBRS isunique, in that it makes available a comparatively large amount ofspectrum (frequency bandwidth) without the need for expensive auctions,and without ties to a particular operator or service provider.Comparable technologies are in development, including for instance DSA,TVWS TV White Space), and LSA (Licensed Spectrum Access).

Moreover, the CBRS spectrum is suitable for shared use betweengovernment and commercial interests, based on a system of existing“incumbents,” including the Department of Defense (DoD) and fixedsatellite services. Specifically, a three-tiered access framework forthe 3.5 GHz is used; i.e., (i) an Incumbent Access tier 102, (ii)Priority Access tier 104, and (iii) General Authorized Access tier 106.See FIG. 1 . The three tiers are coordinated through one or more dynamicSpectrum Access Systems (SAS) 202 as shown in FIG. 2 and Appendix I(including e.g., Band 48 therein).

Incumbent Access (existing DOD and satellite) users 102 includeauthorized federal and grandfathered Fixed Satellite Service (FSS) userscurrently operating in the 3.5 GHz band shown in FIG. 1 . These userswill be protected from harmful interference from Priority Access License(PAL) and General Authorized Access (GAA) users. The sensor networks,operated by Environmental Sensing Capability (ESC) operators, make surethat incumbents and others utilizing the spectrum are protected frominterference.

The Priority Access tier 104 (including acquisition of spectrum for upto three years through an auction process) consists of Priority AccessLicenses (PALs) that will be assigned using competitive bidding withinthe 3550-3650 MHz portion of the band. Each PAL is defined as anon-renewable authorization to use a 10 MHz channel in a single censustract for three years. Up to seven (7) total PALs may be assigned in anygiven census tract, with up to four PALs going to any single applicant.Applicants may acquire up to two-consecutive PAL terms in any givenlicense area during the first auction.

The General Authorized Access tier 106 (for any user with an authorized3.5 GHz device) is licensed-by-rule to permit open, flexible access tothe band for the widest possible group of potential users. GeneralAuthorized Access (GAA) users are permitted to use any portion of the3550-3700 MHz band not assigned to a higher tier user and may alsooperate opportunistically on unused Priority Access License (PAL)channels. See FIG. 2 a.

The FCC's three-tiered spectrum sharing architecture of FIG. 1 utilizes“fast-track” band (3550-3700 MHz) identified by PCAST and NTIA, whileTier 2 and 3 are regulated under a new Citizens Broadband Radio Service(CBRS). CBSDs (Citizens Broadband radio Service Devices—in effect,wireless access points) 206 (FIG. 2 ) can only operate under authorityof a centralized Spectrum Access System (SAS) 202. Rules are optimizedfor small-cell use, but also accommodate point-to-point andpoint-to-multipoint, especially in rural areas.

Under the FCC system, the standard SAS 202 includes the followingelements: (1) CBSD registration; (2) interference analysis; (3)incumbent protection; (4) PAL license validation; (5) CBSD channelassignment; (6) CBSD power limits; (7) PAL protection; and (8)SAS-to-SAS coordination. As shown in FIG. 2 , these functions areprovided for by, inter alia, an incumbent detection (i.e., environmentalsensing) function 207 configured to detect use by incumbents, and anincumbent information function 209 configured to inform the incumbentwhen use by another user occurs. An FCC database 211 is also provided,such as for PAL license validation, CBSD registration, and otherfunctions.

An optional Domain Proxy (DP) 208 is also provided for in the FCCarchitecture. Each DP 208 includes: (1) SAS interface GW includingsecurity; (2) directive translation between CBSD 206 and domaincommands; (3) bulk CBSD directive processing; and (4) interferencecontribution reporting to the SAS.

A domain is defined is any collection of CBSDs 206 that need to begrouped for management; e.g.: large enterprises, venues, stadiums, trainstations. Domains can be even larger/broader in scope, such as forexample a terrestrial operator network. Moreover, domains may or may notuse private addressing. A Domain Proxy (DP) 208 can aggregate controlinformation flows to other SAS, such as e.g., a Commercial SAS (CSAS,not shown), and generate performance reports, channel requests,heartbeats, etc.

CBSDs 206 can generally be categorized as either Category A or CategoryB. Category A CBSDs have an EIRP or Equivalent Isotropic Radiated Powerof 30 dBm (1 Watt)/10 MHz, fixed indoor or outdoor location (with anantenna <6m in length if outdoor). Category B CBSDs have 47 dBm EIRP (50Watts)/10 MHz, and fixed outdoor location only. Professionalinstallation of Category B CBSDs is required, and the antenna must beless than 6m in length. All CBSD's have a vertical positioning accuracyrequirement of +/−3m. Terminals (i.e., user devices akin to UE) have 23dBm EIRP (0.2 Watts)/10 MHz requirements, and mobility of the terminalsis allowed.

In terms of spectral access, CBRS utilizes a time division duplex (TDD)multiple access architecture.

Unaddressed Issues of High Power Devices Initial Registration—

Extant spectrum allocation systems such as the CBRS architecture, whileuseful from the standpoint of e.g., unlicensed spectrum access andreduced contention for spectrum, currently lack mechanisms for initialregistration and authentication of a high-power Consumer PremisesEquipment (CPE) such as a Fixed Wireless Access (FWA) device. Inparticular, in the extant CBRS ecosystem, many devices includinghigher-power CBSD 206 and outdoor FWA devices functioning as CPE aretreated or classified as CBSD devices. As previously noted, Category Adevices can transmit up 30 dBm (lwatt)/10 MHz, while Category B devicescan transmit up to about 47 dBm/10 MHz; hence, in practical terms, aCategory B device may operate out to thousands of feet or more, thepropagation and working range dictated by a number of factors, includingthe presence of RF or other interferers, physical topology of theapplication/area, energy detection or sensitivity of the receiver, etc.

However, on an individual transmitter basis, even the foregoing CategoryB devices are, in comparison to e.g. cellular systems, limited in datathroughput and area coverage. Specifically, to provide a high level ofperformance and greater coverage area, an FWA CPE device has to transmiton comparatively higher power; accordingly, the received Signal-to-NoiseRatio (SNR) and interference ratio is sufficiently high for greater datathroughput (using e.g., 256 QAM, 512 QAM and beyond). However, suchhigher power will violate the Category B EIRP limits enforced in theCBRS system.

High-power CPE are a special class of user equipment for the CBRS band;while current CPE are allowed to transmit at a maximum power 23 dBm, aCPE used for fixed wireless access (FWA) will mostly have an EffectiveRadiated Power (EIRP) in excess of 23 dBm. Therefore, these devices aretreated or categorized as a CBSD (based on their power level), and henceare required to register and be authorized by a SAS prior to startingservice.

FIG. 3 illustrates a typical prior art CBRS registration architecture.The FWA/CPE 303 communicates with a CBSD 206 (the latter backhauled bythe MSO core 307 and connected to a DP 208 via an access network 309such as the Internet, the DP communicative with one or more SAS as shownin FIG. 2 . However, as alluded to above, this standard CBSDregistration architecture does not address certain use cases, includingwhere the CPE EIRP is greater than 23 dBm. For example, in circumstanceswhere CPE 303 is located close to the cell edge or interference signalis strong, the CPE may transmit with EIRP higher than 23 dBm in order tomeet the receiver sensitivity requirement at the CBSD with which it iscommunicating. Generally, a cell edge CPE has a higher probability thanthose CPEs close to CBSD to be constrained by the maximum EIRP 23 dBm,owing to the compensation for the path large loss.

Moreover, in high density environments, the CPE experiences significantinterference from the other users operating in the same frequency oradjacent band. Hence, the CPE may also increase its EIRP in order tocompensate for the interference as well as path loss. In such (orsimilar) circumstances, the CPE with EIRP greater than 23 dBm consideredas high-power CPE, cannot initiate the registration procedure with SAS202.

Furthermore, in the exemplary standard CBRS registration process, theCPE reaching the SAS through the CBSD prior to spectrum allocation canpotentially cause interference to incumbents users, as the CPE locationis not yet known to the SAS, and no interference analysis is performedby SAS. Similar logic applies to other quasi-licensed architectures suchas those previously referenced herein.

Accordingly, there exists a need for a methodology and apparatus toprovide registration and authentication for a high power device (such asa CBRS FWA/CPE) with a wireless network such as those described above,including ideally one which avoids the creation of deleteriousinterference via direct communication between the device and a basestation or access point (e.g., CBSD).

SUMMARY

The present disclosure addresses the foregoing needs by providing, interalia, methods and apparatus for providing registration andauthentication of a served CPE (such as e.g., CBRS FWA devices or othersimilar devices in other context such as DSA or LSA) with a wirelessnetwork.

In one aspect, a method for registration and authentication of a clientdevice (e.g., FWA/CPE) is disclosed. In one embodiment, the FWA/CPEbeing registered is configured to utilize CBRS-band quasi-licensedspectrum, and the method includes communicating data via an alternativeconnectivity channel between the FWA/CPE and an EMS (element managementsystem) that facilitates registration of the FWA/CPE with a SAS via adomain proxy.

In one variant, the method uses an installer application computerprogram (“app”) to read the client device information, and the installerapplication utilizes an MNO (mobile network operator) as theconnectivity link to transmit information to the host (e.g., MSO)network.

In another variant, the method uses an IoT network as the connectivitylink to send the registration information to the MSO network.

In another aspect of the disclosure, a network architecture for deliveryof wireless data to at least one fixed wireless receiver apparatus(e.g., CBRS FWA) is disclosed. In one embodiment, the networkarchitecture includes: a plurality of wireless base stations; acomputerized network controller in data communication with the pluralityof base stations; at least one fixed wireless receiver apparatus; and acomputerized premises device in data communication with the at least onefixed wireless receiver and the computerized network controller. In onevariant, the computerized premises device includes a wireless-enabledmobile device which is logically communicative with both a processexecuting on the receiver and a network registration management entity(EMS and associated database), the latter facilitating “side channel”registration.

In one embodiment, apparatus for establishment of an alternateconnectivity link between the network and the fixed premises device isdisclosed. This alternate link is configured to receive signals from thefixed premises device, and retrieve or/and store premises deviceinformation from/to a data base for registration and authentication.

In another aspect, a wireless premise device is disclosed. In oneembodiment, the device includes a CBRS (Citizens Broadband RadioService)-compliant FWA that is capable of data communication with the3GPP compliant eNB or gNB within CBRS frequency bands. In oneembodiment, the FWA/CPE includes a client manager interface for, interalia, connecting to the host network via the above-mentioned alternateconnectivity link via an “opportunistic” intermediary device such as amobile device. In another embodiment, the FWA includes a low-bandwidthlong-range wireless interface for establishment of the alternate link.

In one variant, the FWA apparatus comprises a premises device operatedby a network operator (e.g., MSO) that is configured to communicatewirelessly with one or more CBSD/xNB devices to obtain high-speed dataservices and wireless backhaul from the premises. In one implementation,the FWA apparatus is configured to operate at a sufficiently high powerlevel so as to be classified as a Category B CBSD CBRS device, and ismounted on the user's premises so as to enable the aforementionedbackhaul for WLAN or wireline interfaces within the premises.

In an additional aspect of the disclosure, computer readable apparatusis described. In one embodiment, the apparatus includes a storage mediumconfigured to store one or more computer programs, such as aregistration/authentication module of the above-mentioned FWA. Inanother embodiment, the apparatus includes a program memory or HDD orSDD on a computerized registration/authentication controller device,such as an MSO EMS or DP.

In another aspect, a method of operating a wireless networkinfrastructure comprising a fixed wireless receiver and at least onebase station is disclosed. In one embodiment, the method includes:utilizing a first communication channel to cause transmission of atleast registration data to a network entity, the first communicationchannel not utilizing the at least one base station; providing to thefixed wireless receiver via the first communication channel at leastradio frequency (RF) spectrum grant data; and based at least in part ofthe provided spectrum grant data, enabling communication within thegranted RF spectrum between the fixed wireless receiver and the at leastone base station.

In one variant, the enabling wireless communication within the grantedspectrum comprises enabling communication within a frequency rangebetween 3.550 and 3.70 GHz inclusive, and wherein the at least one basestation comprises a CBRS (Citizens Broadband Radio Service) compliantCBSD (Citizens Broadband radio Service Device).

In another variant, the enabling wireless communication within thegranted spectrum comprises enabling communication within a frequencyrange between 2.300 to 2.400 GHz band consistent with LSA.

In yet another variant, the enabling wireless communication within thegranted spectrum comprises enabling communication within a frequencyrange between 570 MHz to 790 MHz band consistent with ETSI “White SpacesDevices.”

In another variant, the at least one base station performs at least aportion of said wireless communication utilizing 3GPP-compliant 5G NR-U(Fifth Generation New Radio—Unlicensed) air interface technology.

In a further variant, the utilizing a first communication channel tocause transmission of registration data to a network entity comprisesutilizing a cellular infrastructure to communicate the registration datato a computerized process of a network operator, the network operatoroperating the wireless network infrastructure. In one implementation,the utilizing a cellular infrastructure to communicate the registrationdata to a computerized process of a network operator comprises using theInternet to bridge between the cellular infrastructure and the networkoperator operating the wireless network infrastructure, the networkoperator comprising a multiple systems operator (MSO).

In another variant, the utilizing a first communication channel to causetransmission of registration data to a network entity comprisesutilizing a long-range unlicensed sub-GHz frequency infrastructure tocommunicate the registration data to a computerized process of a networkoperator, the network operator operating the wireless networkinfrastructure. In one implementation, the utilizing a long-rangeunlicensed sub-GHz frequency infrastructure to communicate theregistration data to a computerized process of a network operatorcomprises using a wireless interface of the fixed wireless device tocommunicate directly with a service provider sub-GHz base station.

In a further variant, the method includes using the network entity to:utilize the at least registration data to access a database to obtainsecond data; and utilize at least the registration data and the seconddata to generate one or more communications to a domain proxy process inorder to enable the domain proxy process to generate a request to one ormore SAS processes.

In still another variant, the enabling communication within the grantedRF spectrum between the fixed wireless receiver and the at least onebase station comprises at least transmitting from the fixed wirelessreceiver wireless signals at an EIRP greater than 23 dbm.

In another aspect, a network architecture for delivery of wireless datato at least one fixed wireless receiver apparatus is disclosed. In oneembodiment, the network architecture includes: at least one wirelessbase station; a computerized network controller in data communicationwith the at least one base station; at least one fixed wireless receiverapparatus; and a computerized process in data communication with the atleast one fixed wireless receiver and the computerized networkcontroller. In one variant, the computerized process is configured to:receive data enabling registration and authentication of the at leastone fixed wireless receiver; cause at least registration of the at leastone fixed wireless receiver with a CBRS supervisory process; receivesecond data relating to a wireless spectrum grant from the CBRSsupervisory process or a proxy thereof; and communicate at least aportion of the second data to the computerized network controller andthe at least one fixed wireless receiver to enable the at least onefixed wireless receiver to transact data with the at least one basestation wirelessly using CBRS quasi-licensed spectrum.

In one implementation, the transaction of data using CBRS quasi-licensedspectrum comprises wireless transaction of data within a frequency rangebetween 3.550 and 3.70 GHz inclusive using at least transmittedwaveforms from the fixed wireless receiver at an EIRP greater than 23dbm. The at least one base station performs at least a portion of saidwireless transaction of data utilizing for example 3GPP-compliant 5GNR-U (Fifth Generation New Radio—Unlicensed) air interface technology.

In another variant, the receipt of data enabling registration andauthentication of the at least one fixed wireless receiver comprisesutilizing a cellular infrastructure to communicate the data to thecomputerized process via a cryptographically secure tunnel createdbetween an application computer process operative to execute on a mobileuser device in data communication with the at least one fixed wirelessreceiver.

In a further variant, the receipt of data enabling registration andauthentication of the at least one fixed wireless receiver comprisesutilizing a sub-GHz unlicensed wireless infrastructure to communicatethe data to the computerized process via a cryptographically securetunnel created between an indigenous wireless interface of the at leastone fixed wireless receiver, the indigenous wireless interface alsoconfigured to transact IoT (Internet of Things) data from the at leastone fixed wireless receiver during operation thereof.

In yet a further variant, the network architecture further includes adomain proxy process configured to generate a request to one or moreCBRS supervisory processes configured to operate as CBRS SAS processes.

In another aspect, a registration and authentication computerized entityis disclosed. In one embodiment, the computerized entity includes an EMS(element management system) configured to communicate with deployedCBRS-based field devices such as FWA or their proxies (e.g., anintermediary mobile device with MSO app) for alternate channelregistration and authentication in association with an MSO-based domainproxy (DP) process.

In a further aspect of the disclosure, a method of enabling utilizationof a first wireless transceiver is disclosed. In one embodiment, themethod includes: utilizing a first wireless channel to receive to afirst network entity a subset of data necessary to enable saidutilization; utilizing the received subset of data to access a databaseof data relating to a plurality of wireless transceivers, the access ofthe database obtaining a remainder of the data necessary to enable theutilization; and causing transmission of at least the subset of data andthe remainder of data to a second network entity, the second networkentity configured to generate a request to a third network entity torequest registration of first wireless transceiver and allocation ofwireless spectrum for use by the first wireless transceiver.

In one variant, the first wireless transceiver includes a CBRS (citizensbroadband radio service) fixed wireless access (FWA) device whichrequires transmission of wireless signals at a power level in excess ofa prescribed threshold associated with categorization of the FWA deviceas a device requiring said registration; and the method further includesreceiving, at a base station in data communication with at least thefirst network entity, the wireless signals transmitted at the powerlevel.

In one implementation thereof, the first network entity includes acomputerized network process of a managed content distribution network,the second network entity includes a CBRS domain proxy (DP), and thethird network entity includes a CBRS SAS (spectrum allocation system),and wherein the causing transmission of the subset of data and theremainder of data further includes generating, by at least the firstnetwork entity, one or more messages configured to cause said DP toissue said request, said one or more messages complying with astandardized protocol utilized by the DP.

In yet another variant, the utilizing a first wireless channel toreceive to a first network entity a subset of data necessary to enablesaid utilization includes receiving the subset via at least long-range,low-bandwidth channel, the channel established using at least a secondwireless transceiver in data communication with the first wirelesstransceiver. In one implementation thereof, the receiving the subset viaat least long-range, low-bandwidth channel, the channel establishedusing at least a second wireless transceiver in data communication withthe first wireless transceiver further includes receiving a plurality ofdata packets formatted according to a protocol configured to minimizetransmission overhead, the minimizing transmission overhead configuredto meet a target transmission parameter selected from the groupconsisting of: (i) a target total transmission duration for the subset;and (ii) a target total transmission payload size for the subset.

In yet a further aspect, methods and apparatus for utilizing index orflag data for wireless device registration and authentication isdisclosed. In one embodiment, the index or flag data is selected touniquely identify the wireless device within a given operator's network,and is purposely configured to utilize a minimum of bandwidth fortransmission, and also to allow a recipient process to access a databaseto obtain a richer or more complete set of data as needed for subsequentregistration and authentication, thereby obviating having to transmitthe additional data over a low-bandwidth channel.

In a further aspect, a domain proxy (DP) computerized entity isdisclosed.

In still a further aspect, a system architecture for FWA/CPEregistration with a wireless network utilizing unlicensed orquasi-licensed CPE is disclosed.

In another aspect, a method of facilitating unlicensed or quasi-licensedcell deployment is disclosed.

These and other aspects shall become apparent when considered in lightof the disclosure provided herein.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a graphical illustration of prior art CBRS (Citizens BroadbandRadio Service) users and their relationship to allocated frequencyspectrum in the 3.550 to 3.700 GHz band.

FIG. 2 is a block diagram illustrating a general CBRS system SAS and DParchitecture according to the prior art.

FIG. 2 a is a graphical representation of allocations for PAL versus GAAusers within the frequency bands of FIG. 1 .

FIG. 3 is a block diagram illustrating a prior art CBRS CBSDregistration and backhaul architecture.

FIG. 4A is a functional block diagram illustrating a first exemplary CPEregistration network configuration according to the present disclosure.

FIG. 4B is a functional block diagram illustrating a second exemplaryCPE registration network configuration according to the presentdisclosure.

FIG. 5 is a functional block diagram of a first exemplary embodiment ofan HFC-based distribution and backhaul network architecture according tothe present disclosure.

FIG. 6 is a functional block diagram of a first exemplary embodiment ofan HFC-based CPE registration network architecture according to thepresent disclosure

FIG. 7 is logical flow diagram of the first exemplary embodiment of amethod for registering and authenticating a FWA/CPE with a SAS,according to the present disclosure.

FIG. 8 is logical flow diagram of the second exemplary embodiment of amethod for registering and authenticating a FWA/CPE with a SAS,according to the present disclosure.

FIG. 9A is a ladder diagram illustrating a first embodiment of theregistration and authentication protocol of an FWA/CPE with a SAS (usingan intermediary mobile device) according to the disclosure.

FIG. 9B is a ladder diagram illustrating a second embodiment of theregistration and authentication protocol of an FWA/CPE with a SAS (usinga CPE wireless or wireline interface) according to the disclosure.

FIG. 9C is a ladder diagram illustrating yet another embodiment of theregistration and authentication protocol of an FWA/CPE with a SASaccording to the disclosure.

FIG. 10A is a functional block diagram illustrating one embodiment of anexemplary Consumer Premises Equipment (CPE) according to the presentdisclosure.

FIG. 10B is a functional block diagram illustrating a second embodimentof an exemplary Consumer Premises Equipment (CPE) according to thepresent disclosure.

FIG. 11 is a functional block diagram illustrating one embodiment of anEMS apparatus according to the present disclosure.

FIG. 12 is a functional block diagram illustrating one embodiment of aDomain Proxy (DP) apparatus according to the present disclosure.

All figures © Copyright 2019 Charter Communications Operating, LLC. Allrights reserved.

DETAILED DESCRIPTION

Reference is now made to the drawings wherein like numerals refer tolike parts throughout.

As used herein, the term “access node” refers generally and withoutlimitation to a network node which enables communication between a useror client device and another entity within a network, such as forexample a CBRS CBSD, a cellular xNB, a Wi-Fi AP, or a Wi-Fi-Directenabled client or other device acting as a Group Owner (GO).

As used herein, the term “application” (or “app”) refers generally andwithout limitation to a unit of executable software that implements acertain functionality or theme. The themes of applications vary broadlyacross any number of disciplines and functions (such as on-demandcontent management, e-commerce transactions, brokerage transactions,home entertainment, calculator etc.), and one application may have morethan one theme. The unit of executable software generally runs in apredetermined environment; for example, the unit could include adownloadable Java Xlet™ that runs within the JavaTV™ environment.

As used herein, the term “CBRS” refers without limitation to the CBRSarchitecture and protocols described in Signaling Protocols andProcedures for Citizens Broadband Radio Service (CBRS): Spectrum AccessSystem (SAS)—Citizens Broadband Radio Service Device (CBSD) InterfaceTechnical Specification—Document WINNF-TS-0016, Version V1.2.1. 3,January 2018, incorporated herein by reference in its entirety, and anyrelated documents or subsequent versions thereof.

As used herein, the terms “client device” or “user device” or “UE”include, but are not limited to, set-top boxes (e.g., DSTBs), gateways,modems, personal computers (PCs), and minicomputers, whether desktop,laptop, or otherwise, and mobile devices such as handheld computers,PDAs, personal media devices (PMDs), tablets, “phablets”, smartphones,and vehicle infotainment systems or portions thereof.

As used herein, the term “computer program” or “software” is meant toinclude any sequence or human or machine cognizable steps which performa function. Such program may be rendered in virtually any programminglanguage or environment including, for example, C/C++, Fortran, COBOL,PASCAL, assembly language, markup languages (e.g., HTML, SGML, XML,VoXML), and the like, as well as object-oriented environments such asthe Common Object Request Broker Architecture (CORBA), Java™ (includingJ2ME, Java Beans, etc.) and the like.

As used herein, the term “DOCSIS” refers to any of the existing orplanned variants of the Data Over Cable Services InterfaceSpecification, including for example DOCSIS versions 1.0, 1.1, 2.0, 3.0,3.1 and 4.0.

As used herein, the term “headend” or “backend” refers generally to anetworked system controlled by an operator (e.g., an MSO) thatdistributes programming to MSO clientele using client devices. Suchprogramming may include literally any information source/receiverincluding, inter alia, free-to-air TV channels, pay TV channels,interactive TV, over-the-top services, streaming services, and theInternet.

As used herein, the terms “Internet” and “internet” are usedinterchangeably to refer to inter-networks including, withoutlimitation, the Internet. Other common examples include but are notlimited to: a network of external servers, “cloud” entities (such asmemory or storage not local to a device, storage generally accessible atany time via a network connection, and the like), service nodes, accesspoints, controller devices, client devices, etc.

As used herein, the term “LTE” refers to, without limitation and asapplicable, any of the variants or Releases of the Long-Term Evolutionwireless communication standard, including LTE-U (Long Term Evolution inunlicensed spectrum), LTE-LAA (Long Term Evolution, Licensed AssistedAccess), LTE-A (LTE Advanced), and 4G/4.5G LTE.

As used herein, the term “memory” includes any type of integratedcircuit or other storage device adapted for storing digital dataincluding, without limitation, ROM, PROM, EEPROM, DRAM, SDRAM, DDR/2SDRAM, EDO/FPMS, RLDRAM, SRAM, “flash” memory (e.g., NAND/NOR), 3 Dmemory, and PSRAM.

As used herein, the terms “microprocessor” and “processor” or “digitalprocessor” are meant generally to include all types of digitalprocessing devices including, without limitation, digital signalprocessors (DSPs), reduced instruction set computers (RISC),general-purpose (CISC) processors, microprocessors, gate arrays (e.g.,FPGAs), PLDs, reconfigurable computer fabrics (RCFs), array processors,secure microprocessors, and application-specific integrated circuits(ASICs). Such digital processors may be contained on a single unitary ICdie, or distributed across multiple components.

As used herein, the terms “MSO” or “multiple systems operator” refer toa cable, satellite, or terrestrial network provider havinginfrastructure required to deliver services including programming anddata over those mediums.

As used herein, the terms “MNO” or “mobile network operator” refer to acellular, satellite phone, WMAN (e.g., 802.16), or other network serviceprovider having infrastructure required to deliver services includingwithout limitation voice and data over those mediums.

As used herein, the terms “network” and “bearer network” refer generallyto any type of telecommunications or data network including, withoutlimitation, hybrid fiber coax (HFC) networks, satellite networks, telconetworks, and data networks (including MANs, WANs, LANs, WLANs,internets, and intranets). Such networks or portions thereof may utilizeany one or more different topologies (e.g., ring, bus, star, loop,etc.), transmission media (e.g., wired/RF cable, RF wireless, millimeterwave, optical, etc.) and/or communications or networking protocols(e.g., SONET, DOCSIS, IEEE Std. 802.3, ATM, X.25, Frame Relay, 3GPP,3GPP2, LTE/LTE-A/LTE-U/LTE-LAA, 5G NR, WAP, SIP, UDP, FTP, RTP/RTCP,H.323, etc.).

As used herein, the term “network interface” refers to any signal ordata interface with a component or network including, withoutlimitation, those of the FireWire (e.g., FW400, FW800, etc.), USB (e.g.,USB 2.0, 3.0. OTG), Ethernet (e.g., 10/100, 10/100/1000 (GigabitEthernet), 10-Gig-E, etc.), MoCA, Coaxsys (e.g., TVnet™), radiofrequency tuner (e.g., in-band or OOB, cable modem, etc.),LTE/LTE-A/LTE-U/LTE-LAA, Wi-Fi (802.11), WiMAX (802.16), Z-wave, PAN(e.g., 802.15), or power line carrier (PLC) families.

As used herein the terms “5G” and “New Radio (NR)” refer withoutlimitation to apparatus, methods or systems compliant with 3GPP Release15, and any modifications, subsequent Releases, or amendments orsupplements thereto which are directed to New Radio technology, whetherlicensed or unlicensed.

As used herein, the term “QAM” refers to modulation schemes used forsending signals over e.g., cable or other networks. Such modulationscheme might use any constellation level (e.g. QPSK, 16-QAM, 64-QAM,256-QAM, etc.) depending on details of a network. A QAM may also referto a physical channel modulated according to the schemes.

As used herein, the term “quasi-licensed” refers without limitation tospectrum which is at least temporarily granted, shared, or allocated foruse on a dynamic or variable basis, whether such spectrum is unlicensed,shared, licensed, or otherwise. Examples of quasi-licensed spectruminclude without limitation CBRS, DSA, GOGEU TVWS (TV White Space), andLSA (Licensed Shared Access) spectrum.

As used herein, the term “SAE (Spectrum Allocation Entity)” referswithout limitation to one or more entities or processes which are taskedwith or function to allocate quasi-licensed spectrum to users. Examplesof SAEs include SAS (CBRS). PMSE management entities, and LSAControllers or Repositories.

As used herein, the term “SAS (Spectrum Access System)” refers withoutlimitation to one or more SAS entities which may be compliant with FCCPart 96 rules and certified for such purpose, including (i) Federal SAS(FSAS), (ii) Commercial SAS (e.g., those operated by private companiesor entities), and (iii) other forms of SAS.

As used herein, the term “server” refers to any computerized component,system or entity regardless of form which is adapted to provide data,files, applications, content, or other services to one or more otherdevices or entities on a computer network.

As used herein, the term “shared access” refers without limitation to(i) coordinated, licensed sharing such as e.g., traditional fixed linkcoordination in 70/80/90 GHz and the U.S. FCC's current rulemaking onpotential database-coordinated sharing by fixed point-to-multipointdeployments in the C-band (3.7-4.2 GHz); (ii) opportunistic, unlicenseduse of unused spectrum by frequency and location such as TV White Spaceand the U.S. FCC's proposal to authorize unlicensed sharing in theuplink C-band and other bands between 5925 and 7125 MHz; (iii) two-tierLicensed Shared Access (LSA) based on geographic areas and databaseassist such as e.g., within 3GPP LTE band 40 based on multi-year sharingcontracts with tier-one incumbents; and (iv) three-tier shared access(including quasi-licensed uses) such as CBRS.

As used herein, the term “storage” refers to without limitation computerhard drives, DVR device, memory, RAID devices or arrays, optical media(e.g., CD-ROMs, Laserdiscs, Blu-Ray, etc.), or any other devices ormedia capable of storing content or other information.

As used herein, the term “users” may include without limitation endusers (e.g., individuals, whether subscribers of the MSO network, theMNO network, or other), the receiving and distribution equipment orinfrastructure such as a FWA/CPE or CBSD, venue operators, third partyservice providers, or even entities within the MSO itself (e.g., aparticular department, system or processing entity).

As used herein, the term “Wi-Fi” refers to, without limitation and asapplicable, any of the variants of IEEE Std. 802.11 or related standardsincluding 802.11 a/b/g/n/s/v/ac or 802.11-2012/2013, 802.11-2016, aswell as Wi-Fi Direct (including inter alia, the “Wi-Fi Peer-to-Peer(P2P) Specification”, incorporated herein by reference in its entirety).

As used herein, the term “wireless” means any wireless signal, data,communication, or other interface including without limitation Wi-Fi,Bluetooth/BLE, 3G (3GPP/3GPP2), HSDPA/HSUPA, TDMA, CBRS, CDMA (e.g.,IS-95A, WCDMA, etc.), FHSS, DSSS, GSM, PAN/802.15, WiMAX (802.16),802.20, Zigbee®, Z-wave, narrowband/FDMA, OFDM, PCS/DCS,LTE/LTE-A/LTE-U/LTE-LAA, 5G NR, LoRa, IoT-NB, SigFox, analog cellular,CDPD, satellite systems, millimeter wave or microwave systems, acoustic,and infrared (i.e., IrDA).

As used herein, the term “xNB” refers to any 3GPP-compliant nodeincluding without limitation eNBs (eUTRAN) and gNBs (5G NR).

Overview

In one salient aspect of the present disclosure, methods and apparatusfor registering and authenticating high-power device or CPE (e.g., aCBRS FWA) are provided such that they are allowed to register andoperate in the network without having to utilize their primary (highpower) air interface. In one embodiment, the methods and apparatusutilize quasi-licensed CBRS wireless spectrum in conjunction with (i) anauxiliary or “side” channel for communication; (ii) a domain proxy (DP),registration controller and database; and (iii) a CBSD controller thatallocates frequency, base station, and transmit/receive resources fordelivery of services to a number of installed fixed wireless apparatus(FWA) at user or subscriber premises.

In one variant, the high-power FWA/CPE initially connects to anapplication program operative to execute on an intermediary device(e.g., a UE of a network installer), the latter which establishes achannel and sends the registration information to the DP using a wiredor wireless network interface (e.g., via an MNO cellular network), andreceives a spectrum grant via the same channel.

In another variant, the high-power FWA/CPE initially connects to the MSOinfrastructure for registration via an embedded IoT interface installedin the FWA/CPE. The high-power FWA/CPE sends the registrationinformation to the SAE (e.g., a CBRS SAS) via an IoT interface (andreceives the spectrum grant back through the same channel).

In one variant, an EMS/FWA database is provided to store or/and retrieveFWA/CPE registration and profile data.

Notably, by providing such alternative connectivity to the FWA/CPE,rapid and easy cell deployment and configuration/update is achieved,including in many cases obviating “truck rolls” by leveraging thespecific attributes of the CBRS and MSO infrastructure. In somescenarios, user-based installation, registration, updating and eventroubleshooting is envisioned, such as via an instructive applicationconfigured to execute on the user's mobile device or home PC/laptop orother such consumer device.

The ability of the MSO or other entity to perform a “health check” ofthe CPE through alternate access channels is also advantageouslyprovided, especially during any channel revocation which disconnects theCPE from the MSO backhaul (e.g., the CBSD and its supportinginfrastructure).

The methods and apparatus described herein may also advantageously beextended to other shared-access architectures (i.e., other than CBRS)such as for example DSA, LSA, and TVWS systems.

Detailed Description of Exemplary Embodiments

Exemplary embodiments of the apparatus and methods of the presentdisclosure are now described in detail. While these exemplaryembodiments are described in the context of the previously mentionedwireless access points (e.g., CBSDs) associated with e.g., a managednetwork (e.g., hybrid fiber coax (HFC) cable architecture having amultiple systems operator (MSO), digital networking capability, IPdelivery capability, and a plurality of client devices), the generalprinciples and advantages of the disclosure may be extended to othertypes of radio access technologies (“RATs”), networks and architecturesthat are configured to deliver digital data (e.g., text, images, games,software applications, video and/or audio). Such other networks orarchitectures may be broadband, narrowband, or otherwise, the followingtherefore being merely exemplary in nature.

It will also be appreciated that while described generally in thecontext of a network providing service to a customer or consumer or enduser or subscriber (i.e., within a prescribed venue, or other type ofpremises), the present disclosure may be readily adapted to other typesof environments including, e.g., outdoors, commercial/retail, orenterprise domain (e.g., businesses), or even governmental uses, such asthose outside the proscribed “incumbent” users such as U.S. DoD and thelike. Yet other applications are possible.

Also, while certain aspects are described primarily in the context ofthe well-known Internet Protocol (described in, inter alia, InternetProtocol DARPA Internet Program Protocol Specification, IETF RCF 791(September 1981) and Deering et al., Internet Protocol, Version 6 (IPv6)Specification, IETF RFC 2460 (December 1998), each of which isincorporated herein by reference in its entirety), it will beappreciated that the present disclosure may utilize other types ofprotocols (and in fact bearer networks to include other internets andintranets) to implement the described functionality. For instance, asdescribed in greater detail below, network (e.g., MSO)-specific orproprietary protocols may be used consistent with various embodiments,such as to reduce network transaction overhead on low-bandwidth links.

Moreover, while the current SAS framework is configured to allocatespectrum in the 3.5 GHz band (specifically 3,550 to 3,700 MHz), it willbe appreciated by those of ordinary skill when provided the presentdisclosure that the methods and apparatus described herein may beconfigured to utilize other “quasi licensed” systems or other spectrum,including without limitation DSA, LSA, or TVWS systems, and those above4.0 GHz (e.g., currently proposed allocations up to 4.2 GHz, and evenmillimeter wave bands such as those between 24 and 100 GHz).

Additionally, while described primarily in terms of GAA 106 spectrumallocation (see FIG. 1 ), the methods and apparatus described herein mayalso be adapted for allocation of other “tiers” of CBRS or otherunlicensed spectrum (whether in relation to GAA spectrum, orindependently), including without limitation e.g., so-called PriorityAccess License (PAL) spectrum 104.

Moreover, while described in the context of quasi-licensed or unlicensedspectrum, it will be appreciated by those of ordinary skill given thepresent disclosure that various of the methods and apparatus describedherein may be applied to reallocation/reassignment of spectrum orbandwidth within a licensed spectrum context; e.g., for cellular voiceor data bandwidth/spectrum allocation, such as in cases where a givenservice provider must alter its current allocation of available spectrumto users.

Further, while some aspects of the present disclosure are described indetail with respect to so-called “4G/4.5G” 3GPP Standards (akaLTE/LTE-A) and so-called 5G “New Radio” (3GPP Release 15 and TS 38.XXXSeries Standards and beyond), such aspects—includingallocation/use/withdrawal of CBRS spectrum—are generally accesstechnology “agnostic” and hence may be used across different accesstechnologies, and can be applied to, inter alia, any type of P2MP(point-to-multipoint) or MP2P (multipoint-to-point) technology,including e.g., Qualcomm Multefire.

Other features and advantages of the present disclosure will immediatelybe recognized by persons of ordinary skill in the art with reference tothe attached drawings and detailed description of exemplary embodimentsas given below.

High-Power FWA/CPE Registration/Authentication Architecture—

FIG. 4A illustrates a first embodiment of a service provider networkconfiguration configured to enable FWA/CPE registration as describedherein. It will be appreciated that while described with respect to suchnetwork configuration, the methods and apparatus described herein mayreadily be used with other network types and topologies, whether wiredor wireless, managed or unmanaged.

FIG. 4A illustrates a first exemplary embodiment of the networkarchitecture described herein. It will be appreciated that whiledescribed primarily in terms of CBSD/xNBs 206 which also include EUTRAN(3GPP) compliant eNodeB and/or gNodeB functionality, the latter is by nomeans of requirement of practicing the broader features of theinvention, and in fact non-3GPP signaling and protocols may be utilizedto support the various functions described herein. Due to its currentubiquity (especially in mobile devices or UEs), however, the extant 3GPPprotocols provide a convenient and effective platform which can beleveraged for CBRS-based operation. Moreover, the various aspects of thedisclosure are not limited to CBRS-based frequencies or infrastructure,but rather may conceivably be applied to any fixed architecture wirelesssystem with multiple transmitters and receivers.

In the embodiment of FIG. 4A, the FWA/CPE 403 connects to an MNO network419 for initial registration via an intermediary device such as a UE 466with Certified Professional Installer (CPI) application 415 installedthereon. The CPI application 515 (e.g. a software application installedon a smartphone, tablet, or laptop computer) is the interface betweenthe FWA/CPE 403 and the MS network entity (EMS) 421. In one approach,the Installer application 415 is required to be in communication with(e.g., in proximity of) the FWA/CPE 403 for initial registration.Specifically, the Installer application connects to the FWA/CPE using awired or wireless link 521 (e.g. Ethernet, USB/micro-USB, Bluetooth orWi-Fi). The Installer app 415 reads the cognizant FWA/CPE information(e.g. frequency, signal strength (e.g. RSSI, EIRP), legal entity, deviceidentity, CBSD parameters, or other metrics required in assessing CPEauthentication and/or registration), as described in detail in Table 4shown below.

TABLE 4 Required Parameter Size userId min 72-max 253 [octets] fccId 19[characters] cbsdSerialNumber 64 [octets] cbsdCategory 1 [bit]airInterface radioTechnology 2 [bits] installationParam latitude 4[octets] longitude 9 [octets] height 8 [bits] heightType 1 [bit]indoorDeployment 1 [bit] antennaAzimuth 9 [bits] antennaDowntilt 1[octet] antennaGain 1 [octet] antennaBeamwidth 9 [bits] measCapability 2[bits] professionalInstallerData cpiId max 256 [octets] cpiName max 256[octets] installCertificationTime 13 [bits]In one embodiment, the app 415 utilizes an API call to logic within theprotocol stack of the FWA/CPE 403 (see FIG. 10A), and the API executesand returns the requisite data to the app via the data link between thedevices. Other approaches may be used as well, including HTTP “GET”operations, data push/pull protocols, etc.

After the Installer app reads the FWA/CPE information, the Installerapplication establishes a communication channel with the cognizantnetwork entity (here, the EMS 421) and transmits the data thereto. Inone variant, the channel comprises a VPN tunnel or HTTPS session betweenthe EMS and the Installer app 415 carried over an MNO bearer (e.g., LTEor 5G NR connection) between the UE 466 and a serving MNO infrastructureand the Internet. For instance, the EMS may be accessible via anhttps//url address or the like. Note that the read or push/pull of theFWA/CPE data and the establishment of the Installer app-to-EMS channelneed not necessarily occur simultaneously; in one implementation, theregistration/authentication data can be pulled from the FWA/CPE andstored until an appropriate alternate channel becomes available.

After receipt of the data by the EMS 421, the EMS and FWA/CPE database417 provide the required information for registering FWA/CPE with theSAS to the domain proxy (DP) 404 via the interposed communication linkand protocol 423. In addition, the FWA/CPE profile and other data aresaved in the FWA/CPE database with a unique ID for future use. It willbe appreciated that various scenarios or approaches for assigning an IDto the FWA/CPE 403 may be used consistent with the present disclosure.In one variant, the device 403 is assigned an ID at initial provisioning(e.g., before delivery to the premises for installation). In anothervariant, the ID is assigned during the initialregistration/authentication procedure, such as based on its unique MACaddress (which may be known to the MSO EMS 421 via the DB 417). Yetother approaches will be recognized by those of ordinary skill given thepresent disclosure.

The communication between the SAS 202 and DP 404 is in one embodimentconducted over an extant standardized interface 413, thereby obviatingany special or custom channel or protocol for communications between theMSO DP and the (non-MSO) SAS. As described below, the DP 404 in effectacts as an emulator or normalizer to convert any data obtained from theEMS 421 and DB 417 into appropriate protocol messages for interface withthe (standardized) SAS.

Returning to FIG. 4A, the SAS 402 registers and authorizes the FWA/CPE403 for transmitting and receiving data with the CBSD/xNB via aregistration ans spectrum grant. The registration status/grant data iscommunicated to the FWA/CPE 403 through the domain proxy and thealternate channel between the EMS 421 and CPE Installer application 415.Similarly, the cognizant CBSDs 206 are informed of the spectrumallocation/registration so that the FWA/CPE will be recognized as anauthorized “user” upon initial connection establishment. After theFWA/CPE succeeds in registration, it begins transmission and connects tothe CBSD 206 on the assigned spectrum channel(s).

FIG. 4B illustrates a second exemplary embodiment of the networkarchitecture 450. In this embodiment, the FWA/CPE 403 connects to an IoTnetwork 439 (e.g. LoRa/NB-IoT/SigFox) for the initial registration viaan IoT interface 425 installed on the FWA/CPE 403. Since the IoT network439 supports only a very low data rate in one variant, a pre-establishedunique ID and coded message is used in one embodiment for initialregistration and communication between the FWA/CPE 403 and EMS 421. Inone implementation, a software process executing on the FWA/CPE stack isconfigured to generate the pre-established protocol messages (suitablefor transmission over the IoT network 439) prior to transmission,thereby obviating the need for the UE 466 and associated Installer app415 as in FIG. 4A. However, the embodiment of FIG. 4A is alsoopportunistic (i.e., a UE can be brought into range of the IoT interface425 to use the UE WLAN/LAN/PAN interface to communicate therewith,whereas the LoRa/SigFox infrastructure is generally fixed in nature).Moreover, the MNO data channel can sustain much higher bandwidths/datarates as compared to the IoT network 439. As such, the presentdisclosure contemplates the availability of both approaches; i.e., aFWA/CPE with both IoT interface 425 and support for UE/installer app415, with use of one selected to optimize the desired parameters orfunctionality; e.g., where no IoT service is available or higheralternate channel bandwidths are required (such as for transmission ofimagery or other larger data sets), the MNO option is used, or viceversa.

In one approach, when the FWA/CPE 403 needs to register with the SAS202, the device's unique ID is sent over the IoT access network 439 tothe EMS 421. This unique ID is used to retrieve the associated fullprofile from the FWA CPE database 417. As with the embodiment of FIG.4A, the alternate channel (IoT network 439) is in one implementationused for all of the SAS-related communications through the EMS and DP.Likewise, on the return, the EMS maps the standard SAS messages to setof protocols to enable these messages to be transmitted over thehigh-latency, low bandwidth IoT access network 439.

It will be appreciated that the alternate or side-channel utilized bythe various approaches described herein may be configured forcomparatively low bandwidth/capability, with the amount of data beingtransacted between the FWA/CPE 403 (or Installer app 415) and the EMS421 being comparatively low, since latency is not an issue in many usecases (i.e., there are no QoS or other such requirements). For example,the following calculation demonstrates exemplary values for such data:

Payload range

-   -   Minimum 224 to Maximum 869 octets

Transport layer overhead

-   -   For UDP 20+8=28 octets    -   For TCP 20+20=40 octets

Additional connection setup and maintenance overhead

Payload range with transport layer overhead

-   -   Minimum 252 to Maximum 909 octets        Hence, a typical Tx time range (over an exemplary LoRa sub-GHz        interface with 27 kbps nominal bandwidth) is on the order of 50        to 180 seconds.

In the context of the foregoing, it will be noted that the payloadrestrictions for the exemplary LoRa messages differ across differentgeographic regions (e.g., Europe, Asia, Australia, Americas, etc.). Inthe U.S. for example, at the most stringent spreading factor, thepayload may be restricted to 11 bytes, due channel occupancy limitationsimposed by the FCC. In other regions, the payload may be higher than 11bytes, but the LoRa access has higher latency across all regions. Thismakes these channels non-ideal for higher-overhead protocols such as IPbased communications. However, the LoRa spectrum and technology is veryattractive in the U.S. (and in fact other regions) due to sub-GHzpropagation characteristics (i.e., comparatively long range for LoRacommunications).

Accordingly, in some exemplary implementations of the presentdisclosure, a proprietary small- or low-overhead message protocol isutilized to perform the aforementioned LoRa access exchanges.Specifically, the above-referenced byte limitations are observed, andthe protocol is configured to deliver the requisite data needed by theMSO network entities (e.g., EMS and DP functions) to formulate andtransmit a SAS request. For instance, in one variant, the EMS/FWA-CPEfunction receives a small amount of data (albeit within 11 bytes of LoRapayload), and uses this received data as an “index” for accessing theFWA CPE database to retrieve the complete profile, and use the latter toformulate the SAS messages and send them through the Domain proxy (DP)to obtain the necessary grants to enable the FWA CPE to operate on theCBRS network including at the level of power necessary to properlycommunicate with the target CBSD/xNB(s) serving that premises. In thisfashion, the transmitted data leverages the relevant configuration dataand other information in the MSO network based database, therebyobviating transmission of such data over the comparatively low-bandwidthside-channel (e.g., LoRa), which may take prohibitively long time, and25 necessitate longer technician or installer service calls for the user(thereby detracting from overall user experience).

In one implementation of the foregoing, the transmitted data (index)comprises all or a portion of an FWA/CPE device's MAC address (issued atmanufacture), such as the last several digits, enabling uniqueidentification within the MSO FWA database. In another implementation,the transmitted data is all or a portion of a user-specific orpremises-specific MSO account number. In yet another implementation, thetransmitted data is all or a portion of a device-specific serial number,such as that issued by a manufacturer of the device. It will beappreciated by those of ordinary skill given this disclosure that otherforms and types of data may be used consistent with the disclosure forpurposes of enabling registration/authentication and spectrum grants,including data which is cryptographically protected, data which is FECprotected (e.g., over-coded at e.g., ⅓ or ⅔ rate), data which ismultiplexed (e.g., for concurrent registration of two or more FWA/CPE),and any other ancillary or supporting data which may be required toenable the aforementioned “index” or lookup functionality. Moreover,where another long-range (or suitably ranged) technology with greaterbandwidth is used as the side channel for registration/authentication,more elaborate protocols may be used in such applications consistentwith the present disclosure.

FIG. 5 illustrates an exemplary MSO network architecture for thedelivery of packetized content (e.g., encoded digital content carriedwithin a packet or frame structure or protocol) that may be used insupport of the architectures 400, 450 of FIGS. 4A and 4B, respectively.In addition to on-demand and broadcast content (e.g., live videoprogramming), the system of FIG. 5 may deliver Internet data and OTT(over-the-top) services to the end users (including those of the accessnodes 4) via the Internet protocol (IP) and TCP, although otherprotocols and transport mechanisms of the type well known in the digitalcommunication art may be substituted.

The network architecture 500 of FIG. 5 generally includes one or moreheadends 507 in communication with at least one hub 517 via an opticalring 537. The distribution hub 517 is able to provide content to varioususer/client devices 506, and gateway devices 560 as applicable, via aninterposed network infrastructure 545. The illustrated FWA/CPE 524includes in one implementation an outdoor Fixed Wireless Access (FWA)application of CBRS. In FWA applications, the CBSD/xNB communicateswirelessly with a Customer Premises Equipment (CPE) mounted on thecustomer's house or office (e.g., mounted rooftop, on a pole, etc.); seethe outdoor portion 403 a of the exemplary CPE device of FIGS. 10A and10B. User devices such as 3GPP-compliant UE (e.g., smartphones or othermobile devices) may also be in direct communication with the CBSD/xNB,although due to mobility, such UE are not included within the populationof FWA/CPE reporting to the network controller 610 as describedelsewhere herein.

Various content sources 503, 503 a are used to provide content tocontent servers 504, 505 and origin servers 521. For example, contentmay be received from a local, regional, or network content library asdiscussed in U.S. Pat. No. 8,997,136 entitled “APPARATUS AND METHODS FORPACKETIZED CONTENT DELIVERY OVER A BANDWIDTH-EFFICIENT NETWORK”, whichis incorporated herein by reference in its entirety. Alternatively,content may be received from linear analog or digital feeds, as well asthird party content sources. Internet content sources 503 a (such ase.g., a web server) provide Internet content to a packetized contentorigin server(s) 521. Other IP content may also be received at theorigin server(s) 521, such as voice over IP (VoIP) and/or IPTV content.Content may also be received from subscriber and non-subscriber devices(e.g., a PC or smartphone-originated user made video).

The centralized media server(s) 521, 504 located in the headend 507 mayalso be replaced with or used in tandem with (e.g., as a backup) to hubmedia servers (not shown) in one alternative configuration. Bydistributing the servers to the hub stations 517, the size of the fibertransport network associated with delivering VOD services from thecentral headend media server is advantageously reduced. Multiple pathsand channels are available for content and data distribution to eachuser, assuring high system reliability and enhanced asset availability.Substantial cost benefits are derived from the reduced need for a largecontent distribution network, and the reduced storage capacityrequirements for hub servers (by virtue of the hub servers having tostore and distribute less content).

It will also be recognized that a heterogeneous or mixed server approachmay be utilized consistent with the disclosure. For example, one serverconfiguration or architecture may be used for servicing cable,satellite, etc., subscriber CPE-based session requests (e.g., from auser's DSTB or the like), while a different configuration orarchitecture may be used for servicing mobile client requests.Similarly, the content servers 521, 504 may either besingle-purpose/dedicated (e.g., where a given server is dedicated onlyto servicing certain types of requests), or alternatively multi-purpose(e.g., where a given server is capable of servicing requests fromdifferent sources).

The network architecture 500 of FIG. 5 may further include a legacymultiplexer/encrypter/modulator (MEM; not shown). In the presentcontext, the content server 504 and packetized content server 321 may becoupled via a LAN to a headend switching device 522 such as an 802.3zGigabit Ethernet (or “10G”) device. For downstream delivery via the MSOinfrastructure (i.e., QAMs), video and audio content is multiplexed atthe headend 507 and transmitted to the edge switch device 538 (which mayalso comprise an 802.3z Gigabit Ethernet device) via the optical ring537.

In one exemplary content delivery paradigm, MPEG-based video content(e.g., MPEG-2, H.264/AVC or HEVC/H.265) may be delivered to userIP-based client devices over the relevant physical transport (e.g.,DOCSIS channels); that is as MPEG-over-IP-over-MPEG. Specifically, thehigher layer MPEG or other encoded content may be encapsulated using anIP network-layer protocol, which then utilizes an MPEGpacketization/container format of the type well known in the art fordelivery over the RF channels or other transport, such as via amultiplexed transport stream (MPTS). In this fashion, a paralleldelivery mode to the normal broadcast delivery exists; e.g., in thecable paradigm, delivery of video content both over traditionaldownstream QAMs to the tuner of the user's DSTB or other receiver devicefor viewing on the television, and also as packetized IP data over theDOCSIS QAMs to the user's PC or other IP-enabled device via the user'scable modem 512 (including to end users of the CBSD/xNB access node 206and FWA/CPE 403). Delivery in such packetized modes may be unicast,multicast, or broadcast.

Delivery of the IP-encapsulated data may also occur over the non-DOCSISQAMs, such as via IPTV or similar models with QoS applied.

Individual devices such as cable modems 512 and associated edge devices206, 206 a of the implementation of FIG. 5 may be configured to monitorthe particular assigned RF channel (such as via a port or socketID/address, or other such mechanism) for IP or other types of packetsintended for the subscriber premises/address that they serve. The IPpackets associated with Internet services are received by edge switch,and forwarded to the cable modem termination system (CMTS) 539. The CMTSexamines the packets, and forwards packets intended for the localnetwork to the edge switch. Other packets are in one variant discardedor routed to another component.

The edge switch forwards the packets receive from the CMTS to the QAMmodulator, which transmits the packets on one or more physical(QAM-modulated RF) channels to the CBSDs 206 and ultimately therecipient FWAs 403 and associated client devices. The IP packets aretypically transmitted on RF channels that are different than the “inband” RF channels used for the broadcast video and audio programming,although this is not a requirement. As noted above, the edge devicessuch as cable modems 512 are each configured to monitor the particularassigned RF channel (such as via a port or socket ID/address, or othersuch mechanism) for IP packets intended for the subscriberpremises/address that they serve.

In one embodiment, both IP data content and IP-packetized audio/videocontent is delivered to a user via one or more universal edge QAMdevices 540. According to this embodiment, all of the content isdelivered on DOCSIS channels, which are received by a cable modem 512 orother CM-equipped device 206 a, and distributed to one or morerespective FWA CPE or client devices 403 in communication therewith.

In one implementation, the CM 512 shown in FIG. 5 services a CBSD or xNB206 which in turn services an area which may include a prescribedpremises or venue, such as an apartment building, conference center orhospitality structure (e.g., hotel) via one or more FWA/CPE nodes 403for CBRS-band (3.5 GHz) access. The FWA/CPE 403 may also provideconnectivity for a WLAN router (i.e., the FWA/CPE acting as a radio headfor attached router which provides more localized WLAN services toportions of the premises), which provides e.g., Wi-Fi access for usersat the premises. The FWA/CPE 403 may also communicate wirelessly withnon-MSO CBSD/xNB devices operated by e.g., an MNO for backhaul via thatMNO's infrastructure (not shown).

In parallel with (or in place of) the foregoing delivery mechanisms, theMSO backbone 409 and other network components can be used to transactpacketized data to the user's mobile client device 566 via non-MSOnetworks, including for registration and authentication purposes asdescribed elsewhere herein.

Moreover, so-called “OTT” content (whether tightly coupled or otherwise)can be ingested, stored within the MSO's network infrastructure, anddelivered to the user's mobile device via an interposed ISP (InternetService Provider) network and public Internet 411 (e.g., at a localcoffee shop, via a Wi-Fi AP connected to the coffee shop's ISP via amodem, with the user's IP-enabled end-user device 566 utilizing anInternet browser or MSO/third-party app to stream content according toan HTTP-based approach).

FIG. 6 illustrates an exemplary embodiment of an MSO networkarchitecture 600 useful in implementing the FWA/CPE registration andauthentication functionality according to the present disclosure.

As shown, the illustrated embodiment of the architecture 600 maygenerally include if desired an MSO-maintained CBRS controller 610(which may be disposed remotely at the backend or headend of the systemwithin the MSO domain as shown or at a served venue, or at anintermediary site), an MSO-maintained Element Management System (EMS)421 and FWA/CPE database 417 (as previously described), multipleCBSD/xNB access nodes 206 in data communication with the CBRS controller610 (e.g., via existing network architectures including any wired orwireless connection), as well as any number of CPE/FWA devices 403, andother client devices (smartphones, laptops, tablets, watches, vehicles,etc., not shown). The CBSD/xNBs 206 include in the illustratedembodiment an embedded cable modem 512 used for communication with acorresponding CMTS 539 (FIG. 5 ) within the MSO's (e.g., cable) plantvia cable power and backhaul infrastructure 606, including high-databandwidth connections to the MSO's backbone 409, and electrical powerfor the CBSD/xNB. An MNO (mobile network operator) network 439 also maycommunicate with the MSO network via the backhaul 606, such as forinter-operator communications regarding common users/subscribers;however, this is by no means a requirement of the present disclosure,and in fact the MNO network may be completely dissociated from the MSOnetwork other than having data connectivity for e.g., user-plane (UP)traffic.

It will be appreciated that while a single network controller entity 610is shown in FIG. 6 , the architecture may in fact include two or moresuch controllers, each allocated (whether statically or dynamically) toa subset of the access nodes 206 of the network.

As shown in FIG. 6 , in operation, the Domain Proxy (DP) 404 is inlogical communication with the CBSD/xNB disposed at the service area,node, premises or venue (either directly, as shown, or via MSO backendnetwork infrastructure) and the MSO CBRS network controller entity 610.The DP 404 provides, inter alia, SAS interface for the CBSD/xNB and EMS421 as described elsewhere herein, including directive translationbetween CBSD/xNB or EMS and SAS commands, bulk CBSD/xNB directiveprocessing, and interference contribution reporting to the SAS (i.e., tohelp an SAS tune or update its predictive propagation models and detectrealistic interference issues once CBSDs/xNBs are deployed, theCBSDs/xNBs and even attached FWA/CPE 403 can provide signal strength,phase/timing, and interference level measurements, in addition to or aspart of those provided to the network controller 610 as part ofCBSD/xNB/Beam/slot allocations.

The MSO network controller entity 610 (or entities) in the illustratedembodiment communicates with the DP 404 via an MSO CBRS access network633, which may be a public internetwork (e.g., the Internet), privatenetwork, or other, depending on any security and reliabilityrequirements mandated by the MSO and/or SAS.

As used herein, a CBRS “domain” is defined is any collection ofCBSDs/xNBs 206 that are or need to be grouped for management, whetherlogically or by other scheme; e.g.: according to network operator (NO),according to a serving SAS vendor, by radio path propagationcharacteristics, and/or by physical disposition (e.g., within a largeenterprise, venues, certain geographic area, etc.) In the embodiment ofFIG. 6 , the DP 404 aggregate control information flows to the SAS1 402and/or any participating other SAS (SAS2), which may be e.g., aCommercial SAS (CSAS)), and generates performance reports, channelrequests, heartbeats, and other types of data, including data necessaryfor operation of the spectrum allocation and reassignment algorithmsdescribed in greater detail subsequently herein. In the illustratedembodiment, the DP 404 is operated by the MSO, although it will beappreciated that a third party may operate and maintain the DP 404.

As previously noted, one primary attribute of the disclosure relates toits ability to connect and register a high-power FWA/CPE 403 to SAS;specifically, for high-power FWA/CPE initial registration transmittingat e.g., more than allowable EIRP 23 dBm. It will be appreciated bythose of ordinary skill given the present disclosure that thetransmission periods during which the FWA/CPE comprises a “high power”FWA may vary; i.e., the FWA/CPE may operate as both a high-power andnon-high power device depending on use case and application.

Also notably, since the FWA/CPE 403 are all presumed to be fixed inlocation in the exemplary embodiments, and hence no traditional“mobility” aspects such as those involved with cellular systems need beaccounted for, the functions (and functional allocation) between thevarious components of the network (e.g., RAN, core, etc.) and the client(here, the FWA/CPE), the architecture 600 is more optimized in someregards. Specifically, since the physical/spatial relationships betweenthe FWA/CPE (fixed) and CBSD/xNBs (also fixed) are known a priori, manycalculations can be obviated, and barring any significant other changesin path metrics, one or more given CBSD/xNBs 206 can be used to serveone or more given FWA/CPE devices 403 with some degree of stability andreliability; i.e., a high-power FWA/CPE will likely always need tooperate as such since it's path loss and other physical relationships tothe serving CBSD(s) are known in advance.

To the degree that a new FWA/CPE or CBSD/xNB is installed within thearchitecture (e.g., a new customer is added), this new installation maybe characterized as to its RF propagation characteristics viainstall/startup testing, and the results of the characterization used toassign the new FWA/CPE 403 to a “host” network controller 610 by virtueof the CBSD/xNBs with which the new CPE “best” communicates (as well asother factors such as controller loading).

In the exemplary configuration, the high-power FWA/CPE 403 may connectto the SAS via the alternative MNO network and EMS/DP initially (seediscussion of FIGS. 4A and 4B) for passing registration andauthentication data, as well as other types of data. For example, thisother data may include data relating to the e signals received fromvarious CBSD 206 at the FWA/CPE 403, and this data can be communicatedto the radio path controller 610 To aid in, inter alia, CBSD selectionand configuration to optimize the incipient connection between the(registering) FWA/CPE and the CBSD infrastructure.

In the circumstance where the FWA/CPE 403 may receive signals fromCBSD/xNB 206, but the CPE needs to operate at signal levels higher than23 dBm permitted by the CBRS regulations for CPE devices, the FWA/CPEregisters as a CBSD operating at higher power levels.

When the FWA/CPE succeeds in its registration procedure (e.g., via theEMS 421 and DP 404), the SAS informs the FWA/CPE that it hassuccessfully completed registration via e.g., the alternate channelused. Subsequently, the FWA/CPE can initiate direct requests for channelallocations, such as when a SAS-initiated withdrawal of spectrum isimminent. The SAS performs an assessment of spectrum availability andallocates the FWA/CPE a (new) frequency channel. At this point, FWA/CPEcan start data transmission in the new CBRS band using availablefrequency channel granted by the CBSD/xNB and power levels authorized bythe SAS. If the FWA/CPE cannot complete channel re-allocationrequest/grant before the withdrawal of the existing allocation isrequired, it can again utilize the alternate or side-channel approach asneeded. To this end, the controller 610 or other entity may identify theFWA/CPE 403 that must operate in high-power mode as “at risk” or thelike; and utilize any data it may have regarding impending spectrumwithdraws or revocations in a preemptive manner so as to avoid strandingthe at-risk CPE (i.e., forcing them into use of the alternate channelapproach since they are known to have to operate at high power in orderto communicate with the closest/best CBSD(s)). For instance, in onevariant, the at-risk CPE are given higher priority than non-at-risk CPEregarding new spectrum allocations.

As can be appreciated, there may be a significant number of differentFWA/CPE 403 within the coverage areas of the CBSD/xNBs associated with agiven network controller/schedule 610. Each FWA/CPE installation mayhave markedly different path dynamics and RF signal propagationassociated with it, and as such the exemplary embodiment of the networkarchitecture of FIG. 6 utilizes individualized reporting for each of thedifferent FWA/CPE devices. Accordingly, each different FWA/CPE mayutilize a different combination of alternate channels, fail-over logic(i.e., when alternate channel connectivity is invoked), etc., as well asdifferent time slot scheduling for communications with the variousCBSDs.

Methods—

Referring now to FIG. 7 , one embodiment of the general methodology 700of providing the initial registration for the high power devices (suchas e.g., CBRS FWA/CPEs) according to the present disclosure is shown anddescribed, in the exemplary context of a CBRS-based system with SAS,CBSD/xNBs 206, EMS 421 and database 417, network controllers 610 andFWA/CPE 403 as previously described.

At step 703 of the method 700, the FWA/CPE connects to the Installerapplication running on the UE 466. The Installer application reads orotherwise obtains the necessary CPE information at step 705.

Per step 707, the application sends the obtained registration andauthentication and other requisite data for the FWA/CPE via the MNOnetwork to the EMS 421.

Per step 709, the EMS provide the registration information to the domainproxy (DP) 404.

At step 711, EMS and FWA CPE database 417 stores FWA/CPE profile datafor the CPE 403 for future use, and assigns a unique ID to the FWA/CPEif required (e.g., if the device 403 has not yet been provisioned withan ID).

Per step 713, the DP formats and sends one or more messages to thecognizant SAS, including a request for spectrum allocation.

Per step 715, the SAS registers and authorizes the FWA/CPE, including aspectrum grant if available.

Per step 717, the DP receives the registration data/grant and forwardsit to the EMS 421.

Per step 719, the EMS forwards the received registration/grant data tothe Installer app (e.g., via the alternate channel).

Per step 721, the Installer app forwards the received data to theFWA/CPE 403 via e.g., WLAN or PAN or LAN interface between the devices.

Lastly, at step, 721, the FWA/CPE starts transmitting data and controlinformation to the CBSD/xNB 206 according to e.g., 3GPP protocols inorder to establish a data session in support of user-planecommunications.

If the FWA/CPE subsequently disconnects from the network and decides tore-connect, the re-registration process similar to that as described inFIG. 7 may be used, or alternative approaches such as those describedelsewhere herein (e.g., burst mode attempts at direct registration,reduced power attempts, etc.) may be used as applicable.

FIG. 8 illustrates another embodiment of the method forregistrations/authentication according to the disclosure.

At step 803 of the method 800, the FWA/CPE is initialized. In onevariant, the EMS and FWA/CPE database 417 have assigned apre-established unique ID to the FWA/CPE, and the FWA/CPE 403 isprovisioned with the ID and initialized. In another variant, the CPE hasno initial ID assigned, and is initialized “bare.”

Per step 805, the FWA/CPE uses its indigenous IoT interface (see FIGS.4B and 10B) to connect to the EMS 421 of the MSO network via an IoTnetwork 439 (e.g. LoRa/NB-IoT/SigFox).

Per step 807, the FWA/CPE sends the relevant data needed forregistration and authentication to the EMS. In one variant, since thebandwidth is very low and latency is high on the IoT networkinfrastructure, only the unique ID is sent over the IoT network, and theFWA/CPE full profile is retrieved from the FWA/CPE database 417 by theEMS 421. It will be appreciated, however, that other approaches may beused; e.g., where the CPE 403 has no extant record in the DB 417, thedata sent initially by the device to EMS may include a more complete setof data, up to and including a complete set needed for the requisiteregistration/authentication functions.

At step 809, an ID is created for the CPE 403 if needed by the EMS andstored in the DB 417; the EMS then transmits the ID data back to theFWA/CPE 403 which stores it for future reference.

At step 811, the EMS then transmits the necessary data to the DP 404.

Per step 813, the DP formats and sends one or more messages to thecognizant SAS, including a request for spectrum allocation.

Per step 815, the SAS registers and authorizes the FWA/CPE, including aspectrum grant if available.

Per step 817, the DP receives the registration data/grant and forwardsit to the EMS 421.

Per step 819, the EMS forwards the received registration/grant data tothe FWA/CPE 403 via e.g., the logical channel created over the IoTnetwork 439 between the devices.

Lastly, at step, 821, the FWA/CPE starts transmitting data and controlinformation to the CBSD/xNB 206 according to e.g., 3GPP protocols inorder to establish a data session in support of user-planecommunications.

FIG. 9A is a ladder diagram illustrating a first embodiment of theregistration and authentication protocol of an FWA/CPE with a SAS (usingan intermediary mobile device equipped with Installer applicationprogram) according to the disclosure.

FIG. 9B is a ladder diagram illustrating a second embodiment of theregistration and authentication protocol of an FWA/CPE with a SAS (usinga CPE-based IoT wireless interface) according to the disclosure.

FIG. 9C is a ladder diagram illustrating another exemplary embodiment ofan initial registration and authentication protocol for a high powerFWA/CPE within a CBRS wireless network in accordance with the method ofFIG. 7 (i.e., UE-based alternate channel approach wherein the UEreceives and transmits a full data set).

It will also be appreciated that while the methods of FIGS. 7 and 8illustrate proceeding directly to utilization of an alternate or “side”communication channel for registration/authentication (i.e., presumingthat the FWA/CPE 403 will transmit at above 23 dbm), such methods mayalso be adapted to implement alternate logic in this regard such aswhere for example the Installer app or FWA/CPE itself determines whethersuch alternate channel is required. For example, if other installationsin the area only have required less than 23 dbm (or some otherprescribed power level) historically to establish sufficientcommunication with a serving CBSD for purposes of registration (ascontrasted with normal full bandwidth operation), then the FWA/CPE maybe configured to first attempt to establish physical channelcommunication (e.g., “RACH”) with the CBSD to see if the alternatechannel approach can be obviated. If unsuccessful, then the logic mayfail over to the secondary or alternate channel approaches describedherein. Similarly, the FWA/CPE logic may be configured to utilize dataregarding known CBSD placements or locations to “beam steer” its MIMOarray (if included) towards each of the known CBSD locationssuccessively in order to ostensibly obtain better signalutilization/path loss with respect to the various CBSDs to attempt aregistration/authentication at below 23 dbm.

This logic may also be controlled by the Installer app on the UE 566(FIG. 4A configuration); e.g., after installation of the FWA/CPE device403, the MSO installer may instruct the device to first attempt normalregistration using one or more of the above approaches before resortingto alternate channel connectivity.

FWA/CPE Apparatus—

FIGS. 10A and 10B illustrate exemplary embodiments of CPE 324 (e.g.,high-power FWA or other device) configured according to the presentdisclosure. It will be appreciated that while described in the contextof a CBRS-compliant FWA, the device of FIG. 10 may be readily adapted toother spectra and/or technologies such as e.g., Multefire, DSA, LSA, orTVWS.

As shown in FIG. 10A, the FWA/CPE 403 includes, inter alia, a processorapparatus or subsystem 1002, a program memory module 1004, mass storage1005, CPE controller logic module 1006, one or more front end wirelessnetwork interfaces 1008 for communication with e.g., CBSD/xNB, DP (ifany), the MSO controller 610 and LAN, as well as one or more back endinterfaces 1011 such as for establishment of a WLAN AP within the servedpremises, Gigabit Ethernet or other LAN connectivity, support of home orpremises gateways, DSTBs, etc. as well as for communication with a UE566 for FWA/CPE registration and/or authentication as describedelsewhere herein.

At a high level, the exemplary configuration of the FWA/CPE 403 mayinclude two (2) sub-elements; i.e., an outdoor portion or radio head 403a, and an indoor or processing portion 403 b (as shown in FIGS. 10A and10B). The radio head 403 a in the exemplary embodiment may include eachof the MIMO, MISO or other spatial diversity antenna elements, as wellas RF front end components necessary for receipt and processing of thesignals, including logic to determine radio path parameters of interestsuch as amplitude/RSSI, phase, timing, as well as receive beam forminglogic (e.g., to form two or more discrete receive beams for among otherthings, spatial or azimuthal resolution of the signals received from thevarious CBSD/xNBs 206 in range of the FWA/CPE 403). As such, the radiocontroller logic 1006 (or the beam forming logic) may “steer” theantenna array elements to evaluate or analyze particular azimuth values(which may be precoded into the logic, or fed from the networkcontroller 610 dynamically) to scan and acquire RF signals of interestfrom the various CBSD/xNBs.

As indicated by its name, the CPE outdoor module or radio head 403 a istypically disposed on a premises structure (e.g., rooftop, tower,utility pole, etc.) outdoors so as to minimize intervening interferingstructures and RF signal attenuation as much as possible. The indoorunit 403 b is in communication with the outdoor unit via e.g.,interposed coaxial cable or other medium, and includes a CPE receiverunit 1028 responsible for detecting and demodulating the received RFsignals from different paths and combining them into one logical datastream (and converting to an appropriate protocol for distributionwithin the premises such as IEEE Std. 802.3 Ethernet packets).Combination of the received constituent signals (e.g., user dataaccessed via the assigned TDD slots and carrier(s) and beams) isaccomplished in one embodiment via stream, CBSD/xNB and beam ID data(i.e., each stream of data from the different beam from a differentcontributing CBSD/xNB 206 will have unique ID data that can be used totemporally reconstruct the packet data associated with that stream inproper order and relation).

In the exemplary embodiment, the processor 1002 may include one or moreof a digital signal processor, microprocessor, field-programmable gatearray, GPU, or plurality of processing components mounted on one or moresubstrates. The processor 1002 may also comprise an internal cachememory, and is in communication with a memory subsystem 1004, which cancomprise, e.g., SRAM, flash and/or SDRAM components. The memorysubsystem may implement one or more of DMA type hardware, so as tofacilitate data accesses as is well known in the art. The memorysubsystem of the exemplary embodiment contains computer-executableinstructions which are executable by the processor 1002.

The processor 1002 is configured to execute at least one computerprogram stored in memory 1004 (e.g., a non-transitory computer readablestorage medium); in the illustrated embodiment, such programs includelogic to implement the registration/authentication and radio controllerfunctionality described previously herein. Other embodiments mayimplement such functionality within dedicated hardware, logic, and/orspecialized co-processors (not shown).

In the embodiment of FIG. 10B, an IOT/Bluetooth interface 1066 isintegrated in the FWA/CPE device to connect to an IoT network forinitial registration and authentication. The embodiment of FIG. 10B alsoincludes more comprehensive radio registration logic 1006 to enable,inter alia, direct session establishment with the EMS 421 by the FWA/CPE403 (versus via an intermediary device such as the UE with Installer appas in FIG. 10A).

The software stack of the FWA/CPE 403 is also optionally implementedsuch that CBSD/xNB-to-EMS communication protocols are used to enable theRF detection and reporting functionality previously described, includingCPE functions such as (i) generation and transmission of periodic,on-demand or ad hoc RF detection reports; (ii) receipt of networkcontroller-generated TDD slot, carrier, and CBSD/xNB and wireless beamassignments. The logic 1006 of the stack may also manage other aspectsof FWA/CPE operation, including “intelligent” monitoring and storage ofdata for use in e.g., historical characterizations of the variousCBSD/xNB in radio range of the FWA/CPE in terms of signal strength,signal identity, required signal levels for communication therewith, andother useful data.

EMS Apparatus—

FIG. 11 illustrates an exemplary embodiment of an EMS (elementmanagement system) apparatus 421 configured according to the presentdisclosure.

As shown in FIG. 11 , the EMS 421 includes, inter alia, a processorapparatus or subsystem 1102, a program memory module 1104, mass storage1105, radio registration logic module 1106, one or more back endinterfaces 1111 such as for connection to a LAN or WAN (includingGigabit Ethernet or other LAN connectivity) for connection to the MSO DP404 (or an external DP, not shown), as well as for communication withthe FWA/CPE registration and/or authentication database 417 as shown.

In the exemplary embodiment, the processor 1102 may include one or moreof a digital signal processor, microprocessor, GPU, field-programmablegate array, or plurality of processing components mounted on one or moresubstrates. The processor 1102 may also comprise one or more internalcache memories (e.g., L1/L2), and is in communication with a memorysubsystem 1104, which can comprise, e.g., SRAM, flash and/or SDRAMcomponents. The memory subsystem may implement one or more of DMA typehardware, so as to facilitate data accesses as is well known in the art.The memory subsystem of the exemplary embodiment containscomputer-executable instructions which are executable by the processor1102.

The processor 1102 is configured to execute at least one computerprogram stored in memory 1104 (e.g., a non-transitory computer readablestorage medium); in the illustrated embodiment, such programs includelogic to implement the registration and authentication functionalitydescribed previously herein. Other embodiments may implement suchfunctionality within dedicated hardware, logic, and/or specializedco-processors (not shown).

The software stack of the EMS 421 is implemented and controlled via theregistration/authentication (logic) 1106 such that Installer app (UE)566 to EMS (or FWA/CPE to EMS) communication protocols are used toenable the functionality previously described, including functions suchas (i) receipt of registration and authentication data relating to agiven FWA/CPE, whether from the Installer app or the FWA/CPE itself (orother entity); (ii) establishment of a secure channel (e.g., VPN tunnelor SSL or other approach) between the Installer app (or FWA/CPEregistration process 1006) and the EMS 421; (iii) storage of relevantFWA/CPE registration and authentication data (see e.g., Table 4), aswell as device profile data (e.g., MAC, IP address, etc.) within theFWA/CPE DB 417; (iv) establishment of a communication channel with theMSO DP 404 (or alternatively an external or third-party DP) fortransmission of registration/authentication data and spectrum requeststhereto; (v) receipt of registration and spectrum grant information fromthe DP 404 once the cognizant SAS responds; (vi) transmission of thespectrum grant/registration information to the Installer app or FWA/CPEdirectly; and (vii) transmission of spectrum grant data to the cognizantCBSD(s) with which the FWA/CPE will communicate upon transmission withinthe allocated spectrum. The logic 1106 may also manage other aspects ofFWA/CPE operation, including “intelligent” monitoring and storage ofdata for use in e.g., historical characterizations of the variousCBSD/xNB in radio range of the FWA/CPE in terms of signal strength,signal identity (as described in detail in Table 4), common transmitpower levels used by the FWA/CPE to establish communication with variousCBSDs (e.g., whether greater than 23 dbm or below), and the like.

DP Apparatus—

FIG. 12 illustrates an exemplary embodiment of a Domain Proxy apparatus404 configured according to the present disclosure. It will beappreciated that while described in the context of a CBRS-compliant DP,the device of FIG. 12 may be readily adapted to other components used inother technologies such as e.g., Multefire, DSA, LSA, or TVWS whichfulfill similar functionality therein as the DP of CBRS (e.g., spectrumallocation or registration requests).

As shown in FIG. 12 , the DP 404 includes, inter alia, a processorapparatus or subsystem 1202, a program memory module 1204, mass storage1205, registration request logic module 1206, one or more back endinterfaces 1211 such as for connection to a LAN or WAN 610 (includingGigabit Ethernet or other LAN connectivity) for connection to one ormore SAS 202, as well as for communication with the EMS 421 (FIG. 11 )and the FWA/CPE registration and/or authentication database 417 asshown.

In the exemplary embodiment, the processor 1202 may include one or moreof a digital signal processor, microprocessor, GPU, field-programmablegate array, or plurality of processing components mounted on one or moresubstrates. The processor 1202 may also comprise one or more internalcache memories (e.g., L1/L2), and is in communication with a memorysubsystem 1204, which can comprise, e.g., SRAM, flash and/or SDRAMcomponents. The memory subsystem may implement one or more of DMA typehardware, so as to facilitate data accesses as is well known in the art.The memory subsystem of the exemplary embodiment containscomputer-executable instructions which are executable by the processor1202.

The processor 1202 is configured to execute at least one computerprogram stored in memory 1204 (e.g., a non-transitory computer readablestorage medium); in the illustrated embodiment, such programs includelogic to implement the registration and authentication functionalitydescribed previously herein. Other embodiments may implement suchfunctionality within dedicated hardware, logic, and/or specializedco-processors (not shown).

The software stack of the DP 404 is implemented and controlled via theregistration/authentication request logic 1106 such that EMS/DPcommunication protocols are used to enable the functionality previouslydescribed, including functions such as (i) receipt of registration andauthentication data relating to a given FWA/CPE from the EMS 421; (ii)establishment of a secure channel (e.g., VPN tunnel or SSL or otherapproach) between the DP and the EMS 421 if required; (iii)establishment of a secure channel (e.g., VPN tunnel or SSL or otherapproach) between the DP and the SAS 202 if required; (iv) utilizationof relevant FWA/CPE registration and authentication data (see e.g.,Table 4), as well as device profile data (e.g., MAC, IP address, etc.)within the FWA/CPE DB 417 in order to generate “standard” or typicallyformatted registration and spectrum grant requests to the SAS (e.g., asif the FWA/CPE 403 was utilizing normal registration/grant procedures asin FIG. 3 ); (v) establishment of a communication channel with the MSOEMS 421 for transmission of registration/grant data based on datareceived from the SAS in response to the registration/spectrum requests.

In one exemplary implementation of the DP, standard DP functionality(i.e., WinnForum specified standard CBRS functionality) is used toaggregate the message exchanges between CBSDs and SAS servers (asassisted by the EMS FWA-CPE function and database described above). Thisapproach advantageously allows for utilization within the MSO network ofeffectively “COTS” DP functionality, with the “intelligence” of thesystem for high-power FWA/CPE registration and authentication residingwithin the inventive EMS FWA-CPE database function (the latter whichuses the small amount of data exchanged the FWA CPE over accesstechnologies such as LoRa and NB-IoT as previously described) and usesinformation provisioned with in itself to formulate complete messagesneeded by the DP and SAS for requesting spectrum grants.

It will be recognized that while certain aspects of the disclosure aredescribed in terms of a specific sequence of steps of a method, thesedescriptions are only illustrative of the broader methods of thedisclosure, and may be modified as required by the particularapplication. Certain steps may be rendered unnecessary or optional undercertain circumstances. Additionally, certain steps or functionality maybe added to the disclosed embodiments, or the order of performance oftwo or more steps permuted. All such variations are considered to beencompassed within the disclosure disclosed and claimed herein.

While the above detailed description has shown, described, and pointedout novel features of the disclosure as applied to various embodiments,it will be understood that various omissions, substitutions, and changesin the form and details of the device or process illustrated may be madeby those skilled in the art without departing from the disclosure. Thisdescription is in no way meant to be limiting, but rather should betaken as illustrative of the general principles of the disclosure. Thescope of the disclosure should be determined with reference to theclaims.

It will be further appreciated that while certain steps and aspects ofthe various methods and apparatus described herein may be performed by ahuman being, the disclosed aspects and individual methods and apparatusare generally computerized/computer-implemented. Computerized apparatusand methods are necessary to fully implement these aspects for anynumber of reasons including, without limitation, commercial viability,practicality, and even feasibility (i.e., certain steps/processes simplycannot be performed by a human being in any viable fashion).

APPENDIX I—LTE FREQUENCY BANDS—TS 36.101 (REL. 14 JUNE 2017)

Downlink (MHz) Bandwidth Uplink (MHz) Duplex Equivalent Low Middle HighDL/UL Low Middle High spacing UMTS Band Name EARFCN¹ (MHz) EARFCN (MHz)band 1 2100 2110 2140 2170 60 1920 1950 1980 190 1 0 300 599 18000 1830018599 2 1900 PCS 1930 1960 1990 60 1850 1880 1910 80 2 600 900 119918600 18900 19199 3 1800+ 1805 1842.5 1880 75 1710 1747.5 1785 95 3 12001575 1949 19200 19575 19949 4 AWS-1 2110 2132.5 2155 45 1710 1732.5 1755400 4 1950 2175 2399 19950 20175 20399 5 850 869 881.5 894 25 824 836.5849 45 5 2400 2525 2649 20400 20525 20649 6 UMTS 875 880 885 10 830 835840 45 6 only 2650 2700 2749 20650 20700 20749 7 2600 2620 2655 2690 702500 2535 2570 120 7 2750 3100 3449 20750 21100 21449 8 900 GSM 925942.5 960 35 880 897.5 915 45 8 3450 3625 3799 21450 21625 21799 9 18001844.9 1862.4 1879.9 35 1749.9 1767.4 1784.9 95 9 3800 3975 4149 2180021975 22149 10 AWS-1+ 2110 2140 2170 60 1710 1740 1770 400 10 4150 44504749 22150 22450 22749 11 1500 1475.9 1485.9 1495.9 20 1427.9 1437.91447.9 48 11 Lower 4750 4850 4949 22750 22850 22949 12 700 a 729 737.5746 17 699 707.5 716 30 12 5010 5095 5179 23010 23095 23179 13 700 c 746751 756 10 777 782 787 −31 13 5180 5230 5279 23180 23230 23279 14 700 PS758 763 768 10 788 793 798 −30 14 5280 5330 5379 23280 23330 23379 17700 b 734 740 746 12 704 710 716 30 5730 5790 5849 23730 23790 23849 18800 Lower 860 867.5 875 15 815 822.5 830 45 5850 5925 5999 23850 2392523999 19 800 Upper 875 882.5 890 15 830 837.5 845 45 19 6000 6075 614924000 24075 24149 20 800 DD 791 806 821 30 832 847 862 −41 20 6150 63006449 24150 24300 24449 21 1500 1495.9 1503.4 1510.9 15 1447.9 1455.41462.9 48 21 Upper 6450 6525 6599 24450 24525 24599 22 3500 3510 35503590 80 3410 3450 3490 100 22 6600 7000 7399 24600 25000 25399 23 2000S- 2180 2190 2200 20 2000 2010 2020 180 band 7500 7600 7699 25500 2560025699 24 1600 L- 1525 1542 1559 34 1626.5 1643.5 1660.5 −101.5 band 77007870 8039 25700 25870 26039 25 1900+ 1930 1962.5 1995 65 1850 1882.51915 80 25 8040 8365 8689 26040 26365 26689 26 850+ 859 876.5 894 35 814831.5 849 45 26 8690 8865 9039 26690 26865 27039 27 800 SMR 852 860.5869 17 807 815.5 824 45 9040 9125 9209 27040 27125 27209 28 700 APT 758780.5 803 45 703 725.5 748 55 9210 9435 9659 27210 27435 27659 29 700 d717 722.5 728 11 Downlink only 9660 9715 9769 30 2300 WCS 2350 2355 236010 2305 2310 2315 45 9770 9820 9869 27660 27710 27759 31 450 462.5 465467.5 5 452.5 455 457.5 10 9870 9895 9919 27760 27785 27809 32 1500 L-1452 1474 1496 44 Downlink only 32 band 9920 10140 10359 65 2100+ 21102155 2200 90 1920 1965 2010 190 65536 65986 66435 131072 131522 13197166 AWS-3 2110 2155 2200 90/70 1710 1745 1780 400 66436 66886 67335131972 132322 132671 67 700 EU 738 748 758 20 Downlink only 67336 6743667535 68 700 ME 753 768 783 30 698 713 728 55 67536 67686 67835 132672132822 132971 69 2500 2570 2595 2620 50 Downlink only 67836 68086 6833570 AWS-4 1995 2007.5 2020 25/15 1695 1702.5 1710 300 68336 68461 68585132972 133047 133121 252 Unlicensed 5150 5200 5250 100 Downlink onlyNII-1 255144 255644 256143 255 Unlicensed 5725 5787.5 5850 125 Downlinkonly NII-3 260894 261519 262143 TDD 33 TD 1900 1900 1910 1920 20 A(lo)36000 36100 36199 34 TD 2000 2010 2017.5 2025 15 A(hi) 36200 36275 3634935 TD PCS 1850 1880 1910 60 B(lo) Lower 36350 36650 36949 36 TD PCS 19301960 1990 60 B(hi) Upper 36950 37250 37549 37 TD PCS 1910 1920 1930 20 CCenter gap 37550 37650 37749 38 TD 2600 2570 2595 2620 50 D 37750 3800038249 39 TD 1900+ 1880 1900 1920 40 F 38250 38450 38649 40 TD 2300 23002350 2400 100 E 38650 39150 39649 41 TD 2500 2496 2593 2690 194 3965040620 41589 42 TD 3500 3400 3500 3600 200 41590 42590 43589 43 TD 37003600 3700 3800 200 43590 44590 45589 44 TD 700 703 753 803 100 4559046090 46589 45 TD 1500 1447 1457 1467 20 46590 46690 46789 46 TD 51505537.5 5925 775 Unlicensed 46790 50665 54539 47 TD V2X 5855 5890 5925 7054540 54890 55239 48 TD 3600 3550 3625 3700 150 55240 55990 56739 ¹EUTRAAbsolute RF Channel Number

What is claimed is:
 1. A computerized method of operating a wirelessnetwork infrastructure comprising at least one wireless-enabled deviceand at least one base station, the computerized method comprising:opportunistically utilizing a first communication channel to causetransmission of at least first data to a network entity, the firstcommunication channel not utilizing the at least one base station andrelating to the at least one wireless-enabled device disposed at apremises; providing to the at least one wireless-enabled device via thefirst communication channel at least data enabling identification of agrant of a radio frequency (RF) spectrum; and based at least in part ofthe provided at least data enabling identification of the grant of theRF spectrum, enabling communication within the granted RF spectrumbetween the at least one wireless-enabled device and the at least onebase station.
 2. The computerized method of claim 1, wherein theopportunistically utilizing the first communication channel to cause thetransmission of the at least first data to the network entity, the firstcommunication channel not utilizing the at least one base station andrelating to the at least one wireless-enabled device disposed at thepremises, comprises establishing an ad hoc channel via the at least onewireless-enabled device disposed at the premises.
 3. The computerizedmethod of claim 2, wherein the establishing an ad hoc channel enabledwireless device comprises establishing a channel via a LoRa (Long Range)enabled device.
 4. The computerized method of claim 2, wherein theestablishing an ad hoc channel enabled wireless device comprisesestablishing a channel via an IoT (Internet of Things)-enabled wirelessdevice associated with the premises.
 5. The computerized method of claim1, wherein the transmission of the at least first data to the networkentity comprises transmission of registration data to the networkentity.
 6. A computerized wireless apparatus for use with a wirelessnetwork infrastructure comprising at least one base station and acomputerized network entity configured for transmitting radio frequencyspectrum allocation data, the computerized wireless apparatuscomprising: digital processor apparatus; a first data network interfacein data communication with the digital processor apparatus; a seconddata network interface in data communication with the digital processorapparatus, wherein neither the first data network interface nor thesecond data network interface utilize the at least one base station; anda storage device in data communication with the digital processorapparatus and comprising at least one computer program configured to,when executed on the digital processor apparatus, cause the computerizedwireless apparatus to: select one of the first data network interface orthe second data network interface to utilize for transmission of data tothe computerized network entity; transmit via the selected one of thefirst data network interface or the second data network interface, atleast first data relating to at least one of (i) the computerizedwireless apparatus, or (ii) its surrounding radio frequency (RF)environment; receive via at least one of the first data networkinterface or the second data network interface, at least second data,the received at least second data relating to an RF spectrum grantissued from an RF spectrum allocation entity; and enabling communicationbetween the computerized wireless apparatus and the at least one basestation using RF spectrum identified in received at least second data.7. The computerized wireless apparatus of claim 6, wherein: the firstdata network interface comprises a short-range wireless interfaceconfigured to opportunistically establish a temporary wireless dataassociation with a wireless-enabled mobile device when thewireless-enabled mobile device is within wireless range of thecomputerized wireless apparatus; the second data network interfacecomprises a long-range wireless interface configured to establish an atleast temporary wireless data association with the wireless networkinfrastructure; and the data bandwidth of the first data networkinterface is higher than that of the second data network interface suchthat the first data network interface can support transmission of one ormore data types which cannot be supported by the second data networkinterface.
 8. The computerized wireless apparatus of claim 7, whereinthe selection of one of the first data network interface or the seconddata network interface to utilize for the transmission of the data tothe computerized network entity is based at least on a type of the atleast first data to be transmitted to the computerized network entity.9. The computerized wireless apparatus of claim 7, wherein: the at leastfirst data comprises a unique identifier associated with thecomputerized wireless apparatus, the unique identifier configured toenable the computerized network entity or a proxy computerized processthereof to access, based on the unique identifier received from thecomputerized wireless apparatus, additional data relating to thecomputerized wireless apparatus, the additional data enabling generationof a spectrum request to a spectrum allocation entity, the spectrumrequest on behalf of the computerized wireless apparatus; andutilization of the unique identifier obviates transmission of theadditional data over either the first data network interface or thesecond data network interface such that at least the second data networkinterface may be used to carry the unique identifier with a permissiblelevel of transmission latency.
 10. The computerized wireless apparatusof claim 6, wherein the at least first data comprises a uniqueidentifier associated with the computerized wireless apparatus, theunique identifier configured to enable the computerized network entityor a proxy computerized process thereof to access, based on the uniqueidentifier received from the computerized wireless apparatus, additionaldata relating to the computerized wireless apparatus, the additionaldata enabling generation of a spectrum request to a spectrum allocationentity, the spectrum request on behalf of the computerized wirelessapparatus.
 11. The computerized wireless apparatus of claim 6, whereinthe computerized wireless apparatus initially comprises no identifier,and the at least first data comprises a request for issuance of uniqueidentifier associated with the computerized wireless apparatus, and thereceived at least second data comprises a unique identifier issued bythe computerized network entity or a proxy process thereof responsive tothe request of the at least first data.
 12. The computerized wirelessapparatus of claim 6, wherein the computerized wireless apparatuscomprises a fixed wireless apparatus of a managed content deliverynetwork operated by a multiple system operator (MSO) and configured foruse on a premises of a subscriber of the managed content deliverynetwork, and the at least one computer program is configured to, whenexecuted on the digital processor apparatus, cause the computerizedwireless apparatus to perform the selection, transmission, reception,and enablement of communication pursuant to at least one of an initialinstallation routine or initialization routine.
 13. The computerizedwireless apparatus of claim 6, wherein: the first data network interfacecomprises one of a PAN (Personal Area Network) or WLAN (Wireless LocalArea Network) interface; and the second data network interface comprisesa sub-GHz band data interface configured for long-range communicationrelative to a range of the PAN or the WLAN.
 14. A computerized method ofoperating a wireless transceiver within a wireless networkinfrastructure comprising at least one base station, the at least onebase station used for provision of one or more broadband services to aplurality of wireless transceivers, and a network entity, thecomputerized method comprising: receiving at least one of (i) anapplication programming interface (API) call, or (ii) an HTTP (HypertextTransfer Protocol) GET request, at the wireless transceiver, the atleast one of the API call or the HTTP GET request configured to elicitaccess of first data required by the network entity to further process aradio frequency spectrum request on behalf of the wireless transceiver;responsive to the received at least one of the API call or the HTTP GETrequest, accessing the first data required by the network entity;establishing a communication channel with the network entity, thecommunication channel not utilizing the at least one base station;causing transmission of at least the accessed first data to the networkentity using at least the communication channel; receiving second datatransmitted by the network entity relating to configuration of thewireless transceiver; and utilizing the received second data toconfigure at least a portion of the wireless transceiver to operate inconjunction with the at least one base station for the provision of theone or more broadband services to the wireless transceiver.
 15. Thecomputerized method of claim 14, wherein the receiving of the at leastone of the API call or the HTTP GET request comprises: establishing awireless link between the wireless transceiver and a wireless-enabledmobile device within wireless range of the wireless transceiver; andreceiving the at least one of the API call or the HTTP GET requestissued by an application computer program operative to execute on thewireless-enabled mobile device and transmitted via the wireless link.16. The computerized method of claim 15, wherein the establishing of thecommunication channel with the network entity comprises using at least(i) the established wireless link; (ii) a cellular wireless link betweenthe wireless-enabled mobile device and a mobile network operatorinfrastructure; and (iii) data communication between the mobile networkoperator infrastructure and the network entity.
 17. The computerizedmethod of claim 15, wherein the receiving of the second data transmittedby the network entity relating to configuration of the wirelesstransceiver comprises receiving at least data descriptive of a spectrumgrant, the data descriptive of the spectrum grant having been mappedfrom a first protocol utilized by a spectrum allocation entity to asecond protocol utilized by the wireless transceiver.
 18. A computerizedmethod of operating a wireless transceiver within a wireless networkinfrastructure comprising at least one base station, the at least onebase station used for provision of one or more broadband data servicesto a plurality of wireless transceivers, and a network entity, thewireless transceiver comprising both a first wireless network interfacefor use in the provision of the one or more broadband data services tothe wireless transceiver, and a second wireless network interfaceconfigured to communicate with a distant receiver in support of at leastone of installation or initialization of the wireless transceiver, thecomputerized method comprising: initializing at least a portion of aprotocol stack of the wireless transceiver; based at least on theinitializing, accessing first data required by the network entity tofurther process a radio frequency spectrum request on behalf of thewireless transceiver, the radio frequency spectrum request pursuant tothe at least one of the installation or the initialization; establishinga communication channel with the network entity, the communicationchannel not utilizing either the at least one base station or the firstwireless network interface, and utilizing the second wireless networkinterface; causing transmission of at least the accessed first data tothe network entity using at least the communication channel and thesecond wireless network interface; receiving second data transmitted bythe network entity relating to configuration of the wirelesstransceiver; and utilizing the received second data to configure atleast a portion of the wireless transceiver to operate in conjunctionwith the at least one base station for the provision of the one or morebroadband data services to the wireless transceiver via the firstwireless network interface.
 19. The computerized method of claim 18,wherein the first wireless network interface comprises a 3GPP (ThirdGeneration Partnership Project) LTE (long Term Evolution) or 5G NR(Fifth Generation New Radio) compliant wireless interface, and thesecond wireless network interface comprises a sub-GHz wireless interfacewith EIRP (Equivalent Isotropic Radiated Power) below a prescribed EIRPvalue associated with operation of the first wireless network interfacewithin one or more prescribed frequency bands for the provision of theone or more broadband data services.
 20. The computerized method ofclaim 1, wherein the wireless transceiver comprises a CBRS (citizensbroadband radio service) fixed wireless access (FWA) device.